Rootstack
From the roots of the stack: notes on software design.
Articles
Domain-Driven Design, audited
Rereading Evans's Domain-Driven Design twenty years on, as a source rather than an authority. What the field kept, what it reweighted, what it added, and what it only appears to fight about.
Test Desiderata, remade
Rebuilding Beck's Test Desiderata from the field's evidence. What survives cross-author scrutiny, what gets renamed, and what quietly took sides.
Recently tended
Continuous Integration
Everyone pushes to the mainline at least daily, and every push is verified by an automated build. Running a CI server is not the same thing.
Energized Work
Work only as many hours as you can be productive, and only as many as you can sustain. The renamed 40-Hour Week, improved by the rename.
Extreme Programming
A discipline of software development organized as values, principles, and practices. The second edition rebuilt the practice list so a team can adopt one piece at a time.
Incremental Design
Invest in design every day, in the light of what the system now does. Viable only because three other practices flatten the cost of changing your mind.
Pair Programming
Two people, one running system. The XP practice with the most empirical study behind it, and the results are more qualified than either camp quotes.
Refactoring
Changing a program's structure without changing its observable behavior. Not a named practice in XP's second edition, and load-bearing for two that are.
Slack
Put work in every plan that can be dropped without breaking the promise. The cheapest way to make a schedule believable.
Stories
Units of customer-visible functionality, planned as a promise to talk rather than a written specification. Card, Conversation, Confirmation.