The Rails Way Returns
Back in the days of Rails 1.x, one of the most influential Rails websites was The Rails Way that was run by Rails core team members Jamis Buck and Michael Koziarski. The purpose of the site was to help teach early Rails developers "best practices" in Rails development and did so through code reviews and refactorings of code that were submitted to the site. The site was very influential in helping to push the skinny controller design as well as highlighting many common bad practices.
Unfortunately the site hasn't been updated since October of 2007, that was, until several mornings ago when Michael Koziarski announcing that he is "finally ready to bring The Rails Way back from hibernation". It looks like it will only be Michael writing on the site but in addition to code reviews he states that he plans to add other posts such as:
I’ll be doing some focussed introductory pieces which cover the best practices for a few tricky areas that I see experienced rails programmers getting wrong. I’ll also be doing a few ‘soapboxy’ pieces where I can address misinformation about Rails and Ruby or just advocate a particular piece of technology or code that I think is really cool.
So if you have some code that you wouldn't mind having reviewed in public or you just want to learn from other peoples mistakes - this is a site to keep an eye on.
The first post from the relaunch is Requests Per Second where Koz takes a long at the concept of using "requests per second" as a metric for the benchmarking of your Rails applications.
Support from: acts_as_conference - A two day Rails conference in Orlando, Florida on February 6 and 7. Only $125, free food, a great venue, and lots of top Rails speakers including DHH. Click here to learn more.
January 9th, 2009 at 10:41 pm
Yeah, it will only be me updating the site from now on. I should make that clearer. Thanks for the link.
January 9th, 2009 at 11:38 pm
sorry, but it was jb what had all the good advice.
January 9th, 2009 at 11:45 pm
@blaorph: That's the spirit..!
January 12th, 2009 at 1:12 am
Great to hear ... and the performance post was a good one ... definitely a Rails-style opinionated view on one of the more fluffy aspects of deployment considerations