sprucebruce

3 ms·

1.
by sprucebruce 3y ago
This is exactly what I'm getting at in the blog post. I think the message that it works "if you listen" needs to be front and center so that learners and skeptics can figure out how to apply TDD in scenarios where they don&#x
2.
by sprucebruce 3y ago
It's very common for TDD advocates to claim that testable code is good code - or at least better than it otherwise would be. I don't think that's actually a wild claim. However, I don't think TDD even ensures testability
3.
by sprucebruce 3y ago
There's a great book by Michael Feathers on this very subject called "Working Effectively with Legacy Code". He takes a strong "test first" approach and talks about all the work you have to do when working on a syst
4.
by sprucebruce 3y ago
Howdy - this blog post is responding to folks who do claim that TDD makes it "literally impossible" to design bad systems. This is a fairly common claim among TDD advocates, and I think it makes it harder for learners and skeptics
5.
Work in Small Steps to Improve Stability(aaronbruce.com)
3 points by sprucebruce 3y ago|2 comments
6.
by sprucebruce 3y ago
Zooming in on just how working (and deploying) in small steps can improve system stability. It's odd to me how few orgs have really learned this lesson, so here's my attempt at a brief explanation of the mechanisms involved.
7.
Test Automation Strategy(synapsestudios.com)
1 points by sprucebruce 4y ago|1 comments
8.
by sprucebruce 4y ago
I wrote this piece as a reference for the engineers at our company, but decided today that there's no reason it couldn't be public!