Recent Posts
Archives
- January 2012
- December 2011
- October 2011
- September 2011
- August 2011
- July 2011
- June 2011
- May 2011
- March 2011
- January 2011
- November 2010
- August 2010
- July 2010
- June 2010
- April 2010
- March 2010
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
- 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


Art from limitation: Ruby on rails
We have been learning about Ruby on Rails for the past few months at work. We currently write in C# and ASP.NET. Now it has served us well, but there are some very intriguing things about Rails and the newer frameworks.
This is a powerful notion. I think that fundamentally people like options. We are consumers. I like some things and turn up my nose at others (see OSX vs Vista). I *like* to decide, hunt, gather, and have an escape route. However, my two year old can only decide between two options, give him more than that and his head explodes. Why is that? He can’t process that much data at one time.
Options are like escape plans. If ‘A’ doesn’t work I can always go use ‘B’. As a software developer this is a difficult box. We have a tendency towards the solution with the most options. For instance, Rails is limited, ASP.NET is infinitely configurable. So I want to go with ASP.NET is a customer asks me about Active Directory integration I have a plan. With Rails I can’t do it… No escape plan.
We are missing a huge benefit of the limitations. With the more rapid development environment I can spend more time thinking about the design of the software. What should it do, what opinions does it have, what is it’s essence. That is the kind of software development company I want to run. Creating designed, opinionated, relevant software. I don’t want to wrestle with configurations, compilers, and servers. I want to think about presentation, workflow, and usability.