Spent yesterday’s book time rearranging the Shoulda chapter so as to be more focused on the general ideas than the specific Shoulda interpretation. Today’s job is making sure it all still flows.
So I have something like a half-dozen half-finished blog posts. Until the day some of those become fully finished, here’s a few links.
Simone Carletti has list of practices to follow in your Rails 2.3 app to make it more compatible for an eventual upgrade to Rails 3. I literally just used this article yesterday, building a new Rails 2.3 app with Bundler, rails_xss, and a couple of other nifty things.
Yes, that’s why I tweeted yesterday about the awesomeness of RVM. It was the first time I needed to keep Rails 3 and Rails 2 on my system, so the first time I created a project specific gemset – you can find some articles with instructions in previous link posts. Easy to create, easy to share, easy to set up everybody’s development environment.
This list from Istvan Hoka of Mac OS X tools for Ruby development is a little quirky, but a good overview of what’s available.
I really want to start using Passenger 3. A couple of days ago the Passenger team released another preview post with more cool features. They deliberately bury the lede, though, as they close the post with a strong hint that some of the features will be held for a premium for-pay version. More power to them, I say – free plus paid extras sounds like a good model for them.
Following up on the gems he released a few days ago, James Golick describes his rollout tool for conditionally adding new features. It uses Redis to determine user status for the purposes of conditionally executing code.
I thought about this tweet from Yehuda Katz for a while:
I see where he’s getting this, but I’m not sure that Stack Overflow is all that qualitatively different than picking up advice on the internet in general. It’s just a more efficient way to cargo cult, which would make a great slogan.