Test driven development, Extreme Programming, and many other approaches encourage us to start typing in code, either as a test or as functionality. That’s good advice, but you should never start coding blindly.
Never drive faster than you can see. The trick is to know how fast that is.
Tell em 3 times applies to more than presentations. It works in design too.
Because why you test is as important as what you test.
Because what you test is as important as how you test it.
Testing and the essential attributes of what you’re testing
Cycle time is ALWAYS important
Software development is more than a little like magic.
What is Refactoring and when do you do it?
Some kinds of tests you just don’t want to write
Good habits are good, but there can be too much of a good thing
There is a difference between testing before and after coding
Tests are like cleaning the lint filter on your dryer
Is it someone’s fault, the system’s fault, or a balance of both?
The purpose of testing is to increase confidence for stakeholders through evidence.