Blogmark

On Ruby: Sequel Interview with Jeremy Evans

via jbranchaud@gmail.com

https://on-ruby.blogspot.com/2009/01/sequel-interview-with-jeremy-evans.html

Here a couple fun pearls of wisdom from the vault of time in this 2009 interview with Jeremy Evans, the maintainer of Sequel.

On test coverage:

I test coverage before every release, anything less than 100% gets fixed. 100% code coverage means nothing, but less than 100% code coverage means something.

Refactoring should be in service of something:

There are parts of Sequel that could definitely do with refactoring, but I generally wait to refactor until I'm going do make changes to the code that refactoring will help. I don't refactor for it's own sake.

Finding a balance with when to use Test-Driven Development:

I use TDD when the problem space is known and I know what outputs I want for each input. I'd say I do TDD for new features about 50% of the time, and about 90% of the time for bug fixes.