LLeon Pennings·Sep 7Tech Debt Isn't a Backlog Problem. It's a "Done" Problem.Technical debt is usually described as a bill that arrives later for a purchase made earlier: speed bought on credit, with the cost deferred to some future date. Ask practitioners why debt accumulates10 min read·blog.leonpennings.com
LLeon Pennings·Aug 29The Technical Candy Problem in Software DevelopmentGoodhart's Law, software architecture, and the questions it lets teams stop asking16 min read·blog.leonpennings.com
LLeon Pennings·Jul 21Discovery and Fit Testing: The Two Jobs of a Domain ModelEvery experienced architect has had this happen. A domain expert asks for feature X. An hour of conversation later, it turns out they don't actually need X at all — they need something X happened to b11 min read·blog.leonpennings.com
LLeon Pennings·Jun 7The Invisible Invoice: The Cost of Building Software Without Understanding ItThe Wrong Measure Software doesn't fail when it stops working. It fails when the cost of keeping it working exceeds what anyone is willing to pay. That distinction sounds simple. Its consequences are16 min read·blog.leonpennings.com1
LLeon Pennings·May 21The Properties of Enterprise Software That Lasts"Perfection is achieved not when there is nothing more to add, but when there is nothing more to remove." — Antoine de Saint-Exupéry Introduction Enterprise software is different from other software.28 min read·blog.leonpennings.com
LLeon Pennings·May 19What Is a Rich Domain Model?Most articles about rich domain models get lost in comparisons to anemic models, debates about OOP mechanics, or pattern catalogues. This is not one of those articles. A rich domain model is not a tec17 min read·blog.leonpennings.com52P
LLeon Pennings·May 4AI can build anything except an understanding of what you are buildingThere is a distinction in software development that the industry has spent twenty years pretending doesn't exist. It is the distinction between building software and understanding what you are buildin17 min read·blog.leonpennings.com915CVS
LLeon Pennings·Apr 19Rich domain modelling: a library storyMost software doesn't have a domain model. It has a database schema, a set of service classes that orchestrate calls to it, and a collection of user stories that have been implemented one by one, each13 min read·blog.leonpennings.com1
LLeon Pennings·Apr 10Fast Onboarding of Software Engineers: The Two Learning ModesThere is a persistent belief in software organizations that standardizing on a single framework — Spring Boot being the popular example — makes developers interchangeable across teams. If every system8 min read·blog.leonpennings.com
LLeon Pennings·Apr 7When Distribution Becomes a Substitute for Design — and FailsA lot of modern software architecture—microservices, event-driven systems, CQRS—is not born from deeply understanding the domain. It is what teams reach for when the existing application has become a8 min read·blog.leonpennings.com