I just saw Martin Fowler’s little note about the vocabulary of unit testing, and I thought it was so clear and helpful that I had to share it.
Just seeing the words and the definitions listed side by side clarifies several approaches to what is proabably the hardest part of unit testing – keeping your tests [...]
Posts under ‘Worth Reading’
Unit testing vocabulary
Clear thinking about code reuse
Udi Dahan has just fired off a great post about the pitfals of trying to reuse code – that we make big problems for ourselves by trying to re-use domain-specific code into ways it wasn’t designed to be used. Successful re-use comes about when the code being used is generic enough to actually work in [...]
Feeling a bit of a fanboy
Call me a fanboy if you must, but the people at Coding the Architecture know their stuff. The slides Simon Brown put together on Why Software Projects Fail are a very good, very specific description of what a good software architect can bring to the a project
Test for good developers
I’ve definitely made some interviewing mistakes in my day. Once mistake which I hope too avoid in the future is hiring people who don’t think architecturally, as so eloquently described by Simon Brown over at Coding the Architecture.
I’ve recommended a couple of people who seemed quite competent when talking about their technical skills during the [...]
Another excellent point
How does one arrive at good design, whether it be the architecture for a huge system or the layout for a single interface? Nick Malik over at Microsoft sums it up very nicely:
Design is a process where you consider the problem and then propose multiple, competing, wildly creative solutions. You then narrow down your brainstorm [...]
