Your team writes tests. Good tests.#
And the same categories of bugs keep coming back.
A test catches one failure.
It does not stop the next bug of the same kind from appearing.
A structural constraint does.
It makes an entire category of defect impossible to express, not just caught after the fact.
That is Constraint-Driven Development.
Six levels, from verification up to system design,
each one ruling out a recurring class of bug.
Yesterday's paper asked who develops well.
This one asks how a team stops fighting the same bugs, sprint after sprint.
Part two of the trilogy, for majcon's 20th anniversary. Free, no sign-up.
Tomorrow: the economics of all this. Why changeable code is cheaper code.
Which class of bug keeps coming back in your codebase?
#SoftwareCraft #SoftwareArchitecture
