
A Philosophy of Software Design Summary: Deep Modules Beat Small Ones
John Ousterhout's book in one sitting: complexity is the enemy, deep modules fight it, and 10–20% of your time should go to design. Five ideas to use on Monday.
Tag archive

John Ousterhout's book in one sitting: complexity is the enemy, deep modules fight it, and 10–20% of your time should go to design. Five ideas to use on Monday.

Where should a monolith be split? ZibiWorks finds business boundaries using bounded contexts and ubiquitous language before extracting Fulfillment.

Matt Pocock says to design more abstractions for coding agents and to back them with harsh lint. I tested whether the agent itself can be the designer, with three levers on repeated code across 384 task chains. A written rule and a duplication lint helped one agent out of three. Asking for the refactor helped all three, and what it buys is search more than design.

How immutability, explicit data, pattern matching, and result values change software...

Spring Boot's Quiet Hook for Shipping Configuration: EnvironmentPostProcessor Hi everyone!...
Part 3 of the Grimoire API series. Part 1 built a validated read-only endpoint, Part 2 added...

Imagine you have a domain operation that answers a very common question: “What would happen if we...
Someone asked me last week to stop users typing backticks into a product-name field. Fine. Then...
I approved a pull request last month in about four minutes. Tests passed, the diff was clean, the...

When building applications that orchestrate content across multiple social platforms like TikTok,...
A Roadmap to Crack the System Design Interview
It works. You typed a paragraph and something appeared that does the thing. Twenty minutes. The...