Spoken

Agile “cheat” Sheet: I checked to see if there was a version of this already for "cheat", the command line ruby wiki cheat sheet thing. There wasn't.

Now, there is!

Happy software crafting...

[Indeed. I'm so ripping this off to work locally... thanks Luke!]
Source: Luke Melia

7 reasons I switched back to PHP after 2 years on Rails: SUMMARY: I spent two years trying to make Rails do something it wasn’t meant to do, then realized my old abandoned language (PHP, in my case) would do just fine if approached with my new Rails-gained wisdom. [Since this was highly discussed when it was announced I was wondering what happened when it petered out. Now there’s a lot of folks that know that scrapping a working code base is far more expensive than refactoring. And there’s a bunch more who know that switching languages and frameworks also has a cost. Sooo… this was not a surprising outcome all things considered. I think the end of the story is nice though, as there is nothing like the feeling like you borrowed what you needed and have a system that does exactly what you want (no more and no less).]
Source: O’Reilly Ruby

The Rubinius Sprint: Except for, nobody including me is smart enough to predict which of the Ruby.next implementations is going to have that performance mojo. So, it seems like the only reasonable thing is to bet on all of ’em. One thing that makes this easy is that all the teams get along with each other; a natural outgrowth of Ruby culture, and something from which we can all learn. [Nice, with an interesting sidebar on a great community.]
Source: Tim Bray