May 4 · 17 min read · There 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 buildin
CVSJLCapeStart and 14 more commented
Apr 2 · 20 min read · Most software teams are not struggling because software is inherently chaotic. They are struggling because they are paying enormous amounts of money to keep the wrong machine barely usable. That sound
Join discussion
Mar 18 · 7 min read · Walk into almost any modern enterprise Java codebase and you’ll see the same pattern: controllers, services, repositories, configuration, and a dense web of injected dependencies—often built on framew
Join discussion
Mar 10 · 10 min read · There are two fundamentally different levels in software development. Level 1 — Getting the system to run At this level the goal is straightforward: the application compiles the system deploys feat
Join discussion
Feb 2 · 7 min read · If you plow a field with a Ferrari F40, the field will be plowed. The outcome is correct.The task is completed. Yet the Ferrari is: Excessively expensive for the job Fragile under the wrong conditions Costly to maintain Poorly suited for rain, mu...
Join discussion
Jan 13 · 6 min read · Modern software systems are excellent at moving values around.They are far less effective at preserving meaning. Enums are a telling example. In many codebases, they are treated as glorified constants: labels passed through layers, inspected by if st...
Join discussion
