« swipe left for tags/categories
swipe right to go back »
Thanks for all the feedback and comments on the Learning to Program series with Nate Abbott and Natty Zola from Everlater. In the last post, titled Web Sites and Books for Novice Programmers, I foreshadowed some of the tools that Nate and Natty chose to build Everlater. Now that you know how they got started, here’s what they ended up choosing.
The technology stack that they’ve ended up with has evolved over time. The very first decision – which web framework/backend language to use – was the toughest. Once again, our friend Google appeared – this time for the phrase “web framework comparison.” A few days later, the exploration shifted from simply finding and poking around in the various languages (most notably Ruby/Rails, PHP/CakePHP/CodeIgniter, Python/Django, ColdFusion, .net, and Java), to figuring out the salient points in the debate: speed, ease of use, active development of the platform, security, and cost.
Over beers, Nate and Natty put on blindfolds and threw darts at a board. After incorporating these results into their decision matrix, they chose Ruby/Rails mostly because they felt that it had an active community developing it and seemed to be the easiest to learn the quickest. It took roughly a week to come do a decision, start to finish.
After choosing Ruby as the main language they would be working with, they immediately began searching out every possible Ruby coding Meetup. Through those meetings they became connected with Boulder’s Ruby community which is an amazing group of incredibly smart people. They also found two great people, Charlie and Ryan who began working with Everlater for equity early on and helped make some of the key early decisions.