Rails is amazing. Not only does it let you utilise what is undoubtably the sexiest programming language on earth (name omitted due to obviousness) — it also lets you be productive in that language. Totes amaze.
If you’ve never heard the gospel according to Heinemayer Hansson I’m afraid this article isn’t for you. This is the first post in a series covering how I work with Ruby on Rails, and it assumes that you have some experience with Rails. If you do not, then there really are better ways to spend your time.
This series will tackle all kinds of subject matter: which programs I use to edit and test code; how I structure code running client-side; which gems I employ for solving common problems; which application servers I prefer (hint: It’s Passenger. Not the singer-songwriter, although he’s pretty cool as well.) and how I set them up with nginx/apache; which bear gifs I prefer to leave in as easter eggs — the list goes on. …
If you’re creating a web app these days you’d be hard pressed not to encounter asynchronous programming, either in the form of event handlers, callbacks, promises or what-have-you. It’s essential for providing end users real-time feedback, and the most common way to accomplish it is by using AJAX (the technology, not the K-Pop band).
I fucking love coffeescript.
If you’ve never tried coffeescript, and you’re somehow reading this simply because you saw the words ‘code’ and ‘coffee’ in the title, I strongly suggest heading over to coffeescript.org to give it a once-over — it’s okay, I’ll wait.
Coffeescript is like that cool cousin you never had.
If you didn’t know already, David Heinemeier Hansson, Kent Beck and Martin Fowler hosted a talk about Test Driven Development this past friday. I strongly suggest watching it, but if you haven’t got 30 minutes to spare however, feel free to peruse my mind-blowing thoughts about the talk instead.
So, apparently, TDD came about because Kent Beck read about it in a book when he was 10. No, really. Still, regardless of its origins, there’s no denying that TDD has been widely popular (perhaps to a fault, which is what sparked this talk in the first place), indicating that many developers enjoy the workflow it encourages (or are just afraid of doing anything else, because this is the right way to do something). …