As a guy who recently switched from years of ASP.Net MVC to Rails, I read this post and wanted to shout... "Watch out everybody, he's hitting the database!!!"

As a guy who recently switched from years of ASP.Net MVC to Rails, I read this post and wanted to shout... "Watch out everybody, he's hitting the database!!!" Ruby is a great language that I love, but this is one of those cases where Ruby's conciseness and readability hide a TON of complexity. And complexity in tests is death. I've seen it for myself -- there's a lot of technical debt interest in those tests. It looks manageable at the beginning, especially within the scope of a blog post, but when the app grows and grows and grows, the tests fail.