3rd-party code still needs tests

[ original gist 28 March 2013 ]

“If there are no tests, it does not work,” a former colleague said, who could have added, “whether your code or someone else’s.”

I’m not the first to say it but it needs re-stating: 3rd-party libraries are no guarantee that your code continues to behave as expected.

If one of the duties of your work is making sure you’re not introducing bloat or cruft or inefficiencies or bugs or unexpected behavior, then you’re cutting corners if you don’t have tests, whether you use 3rd-party code or not.

Continue reading “3rd-party code still needs tests”


The Plus & Minus of TDD ~ a commenter’s great response to Cedric Beust.

[ original gist 4 AUG 2013 ]

Text below is not my own; it is copied from a comment on Cedric Beust’s blog at


Here are some of the things I like about TDD:

Continue reading “The Plus & Minus of TDD ~ a commenter’s great response to Cedric Beust.”

How well does TDD work when testers are writing the tests?

[ original gist 3 June 2013 ]

The point of agile is lost when teams fixate on roles and responsibilities. Fixed roles (“dev”, “qa”) harm you in the long run – and the long run is always up sooner than you think.

That’s a noisy prelude to my answer to the question: Should QA Write Unit Tests?

Continue reading “How well does TDD work when testers are writing the tests?”

Hello, world (again)

[originally posted 2013-08-11]

Thanks for stopping by.

I used to maintain this blog on github using Hexo, a Node.js module supporting markdown. I’ve switched over to wordpress online once I found it supported markdown (in the Settings section) so I wouldn’t have to go through all the rebuilding and deploying for such simple things as fixing a typo.

Continue reading “Hello, world (again)”