You, faithful reader (all one or two of you), probably suspect me of being a lazy procrastinator who has neglected his blog and left key portions of the story untold. You’re probably right, but the reason I’ve been procrastinating is that I haven’t wanted this journey to end.
I’ve always sucked with endings. When I wrote fiction, I dreaded getting to that point when I had to start thinking about wrapping up the tale. I didn’t want to stop exploring the world and the characters I had created. With Wyncode, I wanted to keep driving onward, learning and exploring new concepts with my amazing classmates.
But in fiction as in life, you can only avoid the ending for so long. A reluctant ending is better than none at all, so I will do my duty and bring this journey to its conclusion.
For the final project, my team built thebulk.co, a crowd sourcing site to buy items in bulk. The idea originated from one of my teammates. She had extensive experience as a project manager and had worked on big projects like HBOGo, so she was a natural lead for the team. We ran into tons of blockers throughout the two weeks we worked on the app, but we stuck together and overcame them all. We had a MVP (minimum viable product) ready just a few hours after the scheduled code freeze. And that was my fault, because I thought it would be a simple matter to set up AWS hosting for our images on the final night of work, and not only did that setup take up the entirety of that final night, it overflowed into the entire morning and past the code freeze.
From now on, I set up AWS right from the start.
With the projects on code freeze, the last week of Wyncode consisted of advanced lectures and presentation preparations for Pitch Day VI. We all learned quickly that presenting is hard work, and we sucked at it. Luckily, we had the entire Wyncode team there to help us prepare. We practiced our presentations a handful of times in front of live audiences, including a full rehearsal at Live Ninja’s #wafflewednesday.
Our presentations that morning were disastrous. And the next night, we had to perform in front of hundreds of people, judges, companies that might hire us, and venture capitalists. One of the things I’m most proud of is the improvement all the teams made from that morning to Pitch Day.
We all killed it that night, and it was an amazing night with tons of surprises. It started with our head TA announcing he was leaving and taking a job with Udacity in San Francisco. Needless to say, we were super excited for him, and that set the celebratory tone for the night. And to end the night, we learned that one of our very own classmates, whom we had taken to calling Superman, was going to take over the head TA position! He has big shoes to fill, but I’m confident he’s going to soar.
At the end of the night, I had the opportunity to chat with a few people looking to hire coders. I collected and distributed business cards and followed up, but nothing really came out of those conversations. Luckily, I had already been in talks with one company to complete a project for them as a consultant.
That night, I celebrated with my girlfriend, my brother (who flew in from Baton Rouge to attend the event), and my parents. That weekend, I celebrated with my old friends who I had been badly neglecting over the two month bootcamp. And then Monday.
Up at six a.m. Back to my old job. Most of my classmates were back at The LAB, collaborating on projects and studying to improve their skills. I was in my small, spartan office. The room is about the size of a small bathroom. It’s freezing because the old AC at the school can’t regulate temperatures right. No windows. There’s one poster, a Heat Championship team, on the wall, and lots of papers thumbtacked to a cork board. Papers with medicaid codes, CHC processes and cross-battery assessment, bell curves, language dominance classifications, certificates from trainings, and my go-to reference for projective assessments. All my psychological test kits stacked in the corner like kindle for a funeral pyre. My entire library was boxed and taped shut.
I had stripped my office before the end of the school year with the intention of never going back. And yet, there I was, unable to believe Wyncode was over, and dreading losing coding time because I had to evaluate the next kid on my case load. I had told myself that if I ever stepped foot in that office again, I’d be a big fat failure. It would mean that I wasn’t smart enough, that I couldn’t learn something new, that I was too old to start a whole new career.
That kind of thinking led to a rough start to the week. At The Lab, they were having Wynterviews each day, during which teams from hiring partners came and interviewed each of the final-project-teams. With work, I had a hard time making it to the interviews, and I hadn’t received any solid responses from my resume submissions on job boards. I saw myself at sixty, sitting that that tiny closet of an office, shuffling the same papers around after completing yet another evaluation.
And then Thursday, I got a call from the company I had been in talks with to complete their project. I had been in competition with a firm from Boca, and they had decided to go with me. Could I meet with them on Saturday to kick off the project?
And like that, I had a job.
I’ve been winding down my last two weeks, leaving things in order for whoever comes to take over after me. And of course, I’ve been studying my ass off, trying to build my skills so that I can be effective on my first gig. So really, the end is just the beginning, because the greatest thing about wynning code, is that the journey never ends.
A HUGE thank you to the entire Wyncode team and all my classmates for making these last two months truly special. And I can’t finish without mentioning our head instructor one more time, Ed Toro. If any future students are reading this, be prepared. Ed’s instruction moves blazing fast. It’s impossible to keep up (unless you’re Superman). Don’t fight it. Embrace it. Realize that Ed is trying to download decades of coding experience and knowledge into your brain in just nine weeks. You’re not going to get it the first time…in fact, you might come back few months later to tell him about this cool new trick you learned, for him to tell you that trick was covered in slide 38 of the Ruby methods lecture during week two. So until the day that he designs a Matrix like interface to make you a programmer in an hour or two, just do your best keep up.
And to anyone starting out on their own coding journey, go start hacking!
“A computer is like a violin. You can imagine a novice trying first a phonograph and then a violin. The latter, he says, sounds terrible. That is the argument we have heard from our humanists and most of our computer scientists. Computer programs are good, they say, for particular purposes, but they aren’t flexible. Neither is a violin, or a typewriter, until you learn how to use it.” ― Marvin Minsky