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.
Topic
Programming
A collection of 27 issues
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 Routing Graph from OSM: Transition Constraints and Path Constraints
Why a road network needs explicit constraints, not just nodes and edges
Why Simple Changes Rarely Stay Simple
How software systems become resistant to simple change
Building a Durable Telemetry Ingestion Pipeline with Rust and NATS JetStream
Why Direct-to-Database Ingestion Fails at Scale and What Actually Works
Beyond Enterprise OOP: Building Clear, Composable Systems with PostgreSQL and Rust
PostgreSQL Guards the Facts, Rust Defines Intent, and Clarity Scales with the System
Simplicity Wins: Command Context Consistency
How Self-Contained Features and Event Logs Replace Legacy Models
Context, Rules, Decisions: The Formula for Better Domain Models
Moving Beyond Mutable Objects to Explicit Business Logic