10 Technical Papers Every Programmer Should Read (At Least Twice) 10 Technical Papers Every Programmer Should Read (At Least Twice) this is the second entry in a series on programmer enrichment Inspired by a fabulous post by Michael Feathers along a similar vein, I’ve composed this post as a sequel to the original.
That is, while I agree almost wholly with Mr. Feather’s1 choices, I tend to think that his choices are design-oriented2 and/or philosophical. In no way, do I disparage that approach, instead I think that there is room for another list that is more technical in nature, but the question remains, where to go next? Apprendre HTML CSS PHP Javascript JQuery MySQL Bootstrap Twitter.
What are you interested in learning? Lyon Ruby Brigade. Ember.js - A framework for creating ambitious web applications. Webmaker. Compare web frameworks. The Hour of Code. W3Schools Online Web Tutorials. Tutoriels. The Rust Programming Language. Créez un site Web gratuit. OpenClassrooms, Le Site du Zéro - Les cours les plus ouverts du Web. Ruby on Rails Tutorial. Michael Hartl Contents Foreword My former company (CD Baby) was one of the first to loudly switch to Ruby on Rails, and then even more loudly switch back to PHP (Google me to read about the drama).
This book by Michael Hartl came so highly recommended that I had to try it, and the Ruby on Rails Tutorial is what I used to switch back to Rails again. Though I’ve worked my way through many Rails books, this is the one that finally made me “get” it.