Quotes from Russ Olsen

Write the tests first, or second, or third. But write the darned tests.

That voice you hear in your head, the one whispering that you need to add some comments, may just be your program crying out to be rewritten.

names of methods that do something unexpected, or perhaps a bit dangerous.

Remember, a great way to avoid broken code is to have less of it. The code that you never write will work forever.

In coding, as in carpentry, you need the right tool for the job.

It comes down to this: Ruby is a language for grown-ups; it gives you the tools for writing clear and concise code. It's up to you to use them.

a great way to avoid broken code is to have less of it. The code that you never write will work forever.

Let's face it: Despite shelves full of books on software architecture, enough UML diagrams to fill an art museum, and design meetings that seem to last longer than the pyramids, building software mostly comes down to writing one method after another.

How do you test just the one class when that class needs an entourage of other classes to work? What you need are stubs and mocks.