Shorter pieces, published here first and mirrored to dev.to and Medium. Each one takes a single argument from the books and works it out at article length — the canonical copy lives here.
Type inference has refused to guess for fifty years, and build systems learned the habit. Decomposition methods never did: feed one an underspecified system and you always get a diagram. Three clauses, the five things they forbid, and a definition of engineering stated as a ratio rather than a badge.
Strategic domain-driven design does not rest on tactical DDD, which means you can keep one and replace the other. How to annotate a context map so it feeds a change-driver decomposition instead of an aggregate model.
A complete backend test strategy: four kinds of test, each derived from a property of the code rather than chosen from a convention, plus the rules that fall out and why the result beats picking a ratio.
How structural patterns turn code review from a matter of taste into something two reviewers can agree on — the first article in the series.