Thanksgiving 2008: What We’re Thankful For (In Rails)
Since it's Thanksgiving and all, I asked our Rails developers to briefly mention something in Rails that they are thankful for. You'll notice some common threads -- nobody consulted with anybody else as far as I know.
Anthony Caliendo
I'm thankful for the "convention over configuration" mindset, as it saves me so much time and removes all the plumbing and wiring I needed to do when developing java apps just to get it running.
Jason Sendelbach
I am thankful that Ruby on Rails has conventions and code that reads like prose. Because of this, I can join an existing project and be an effective resource immediately. If I am fixing a bug, I simply look at the URL to figure out where to start. If the code is good (most of the code in Models and Helpers and not in the Controller), there are few bugs (did I mention the code was generated with TDD) and I can quickly start coding without much overview from any of the other developers. The entire project and code is self explaining. There is almost zero ramp up time. Thanks Rails (and Ruby).
Josh Symonds
Definately ActiveRecord. Particularly associations and association methods, and named scopes (because they feel like association methods but on one model).
Sharad Jain
I am sure ActiveRecord is the crownjewel. Outside of that, support for testing (unit, funcational) and supporting classes inside of rails are great.
Standardization of how libraries are installed (gems, plugins) etc. and convention of configuration in general is also something that I am thankful for.
Karthik Muthupalaniappan
I think the best thing for me about Rails is it lets me worry only about how I should/can code a functional requirement of an application by taking care of most of the other configurational/operational aspects of the application
John McCaffrey
Thorough implementation of Regular expressions throughout ruby and rails.
Noel Rappin
I get to go last, so I won't repeat anybody else...
I honestly love the ActiveSupport library, with all its 2.days.ago and 10.kilobytes and even array.second. I'm thankful for the attitude encapsulated by all these methods -- "if I needed to this, a lot of other people probably will, and I want to make sure they don't have to write it again". It's DRY at the community level, and it's part of what makes working in Rails so satisfying.
Have a great holiday weekend, everybody. Thanks to all of you that read and comment.
Topics: Ruby on Rails
Leave a comment
About Pathfinder
Follow the Blog
-
Get a monthly update on best practices for delivering successful software.
Subscribe via email
Subscribe via RSS
Categories
Topics
Archives
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- February 2009
- January 2009
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- September 2007
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- March 2007
- February 2007
- January 2007
- December 2006
- November 2006
- October 2006
- September 2006
- August 2006
- July 2006
- June 2006
- May 2006
- April 2006
- March 2006
Blogroll
Recent
- Elements of Testing Style
- Aesthetics and Web Design
- Asterisk-Java Testing with Groovy
- 3 Misuses of Code Comments
- Fluently NHibernate
- Digging a Hole and Covering it with Leaves — The Software Development Version
- The Importance of User Experience - Do You Understand It in Your Bones?
- Writing Your Own Protocol With NSURLProtocol
- What’s In Your Dock: iPhone edition
- Feature Fatigue

