spike-then-stabilize-vs-tdd

If you could write a spike well enough to wrap tests around it later and stabilize it into production code, why would you throw it away? If spiking became easier as a result of not throwing it away, would you do it more?

blog-post-beyond-tdd

Is this at all related to what Martin Fowler said about sacrificial-architecture?

podcast-giant-robots-119-pete-hunt#scales-so-well

talked about how React scales well, meaning that there's never a point when the proof-of-concept needed to be fundamentally changed to become the real thing.

 
talk-angel-list-doing-the-wrong-things-the-right-way#no-tests

They used to do TDD but found it to be "too slow, foreign, and dogmatic". Instead, now they are just "ready for bugs"

"Alarms on everything"

"Pipe them to email, chat, and SMS"

"Bug fixes are a top priority"

"Tests are fine, but not compulsory"

 

People

person-martin-fowler person-liz-keogh person-pete-hunt