Sitemap

It might be our little R2 unit. Hit the accelerator!

3 min readNov 18, 2014

After a short application campaign I settled on General Assembly as my accelerator of choice. While the primary factor that decided me on them was their cohort timing (starting today instead of mid-January or later), I was also impressed by their commitment to having a human touch in the process. Other coding academies seemed to have a lot of trouble with simple communication, but by comparison General Assembly was putting on a charm offensive. While I suppose it was possible they were merely desperate to fill the seats in their soon-to-launch cohort, I nevertheless appreciated feeling like I was worth the time to have human handlers calling me and meeting me in person for non-threatening info sessions instead of curt auto-generated emails and faceless Google Calendar invites for technical interviews.

I was glad that I had a decent amount of experience with almost everything we covered today (with the exception of the care and feeding of git), as I spent most of the day wrestling with my virtual machine instead of following along as closely as I would have liked. I found myself sparing some thought for regret and whether I should admit defeat and buy a Macbook during the afternoon but finally broke through thanks to a handy Github repository that had the code I needed. Just in time to have missed most of the instruction on git, of course.

Get Ben Crane’s stories in your inbox

Join Medium for free to get updates from this writer.

Deciding to do General Assembly on “hard mode” (using a Windows laptop instead of a Macbook but using Vagrant to virtualize an Ubuntu box for me to SSH into using Cygwin so I can have a command line while Vagrant synchronizes the files from the virtual machine to my host machine) is feeling like the right decision so far. It’s harder because the instructors have to ride herd on the whole class so any of my weird issues are problems I have to resolve on my own (in addition to the whole forcing a square peg into a round hole of trying to use a Windows machine in ways it’s explicitly not designed to do). The practice with virtual machines and SSH configuration is something I think I will use a lot in the future but even if I won’t it’s at least been oddly fun to try to figure it out.

I might lose a few steps in the early going but I definitely feel like I can afford that as I am much more comfortable using the command line than the majority of the class and I think I am more comfortable using VI than the instructors. That last one is quite a boon as my research and futile attempts yesterday indicate to me that I won’t be able to issue a command telling the computer to use Sublime to open text files (thanks Microsoft).

My main struggle is going to be using git correctly. I will need to work harder on wrapping my head around that because it’s essential. So my extracurricular reading is going to be Pro Git for the foreseeable future. I tend to be visual and like to issue a command and verify that it happened, which I think is very possible in git but I’m not used to the way it does things. Seeing as how it’s kind of the backbone of version control and everyone uses it I am pretty confident I can figure it out as long as I keep plugging away at it.