How to write code that doesn't suck with Ruby on Rails

Buzzwords like BDD, TDD, ATDD, RDD, and DDD may have convinced you that writing great, maintainable code is just a matter of following a few simple instructions. All you need to do, you've been told, is write good unit tests, and make sure you have a good CI suite to call you out when your tests fail.

Confreaks made sure that their tests covered those interfaces, not merely the individual methods that were being run. Along the way, thry learned lessons about testing, writing code to be used by others, loose coupling, public interfaces, and a whole lot more.

Join Yehuda Katz as he examines some of those lessons, using Merb as a lens. He'll be challenging many orthodoxies of today's Ruby programmers, so if you fear change, stay away. On the other hand, if you're looking for some new ways to think about writing complex systems, testing them, and making your tests resilient to even the most invasive refactoring, join Katz. Let's step through the looking glass together.

See how to write code that doesn't suck with Ruby on Rails.