Why Your Software Cannot Explain Its Business Decisions
Make the path from command to outcome explicit in the architecture. How you store state, relational or event-sourced, is a separate decision.
More issues
Rethinking REST API Design
Go Beyond CRUD to Uncover Domain Behavior
Thinking in Events
Separating the Modeling of What Happened from the Decision of How to Store It
Simply Event Sourcing
Aggregates Were Never Required — Command Context Consistency and DCB’s Tag-Based Contract
Why the Domain Is Defined by Domain Capabilities, Not Object Models
Additive Domain Evolution Through Autonomous Capabilities
Request Processing Units and Reactors
Decoupling User Interactions from Internal Domain Capabilities
Functional Core / Imperative Shell for Agentic Coding
How Repository Structure, Feature Slices, and Project-Level Skills Guide Coding Agents Toward Self-Contained Features
Building a Road Network from OSM: Roads, Segments, and Directed Edges
A practical look at how a routing graph emerges from OSM nodes and ways
Building a Routing Graph from OSM: Transition Constraints and Path Constraints
Why a road network needs explicit constraints, not just nodes and edges
Road Networks Are Execution Models, Not Stored Geometry
On semantics, projection, and the architectural difference between stored geometry and executable movement constraints