Actionable insights in daily software development


Twenty years in, still learning - writing down what sticks.

Google Drive as just another filesystem

The test is removal, not addition


Safe destructive operations through a planning phase

Decide first, act later


Transparent multi-tenancy with the engine pattern

The domain never asks


Synchronous domain events

Correct before fast


Email verification as a separate bounded context

When a flag becomes an entity


When your reverse proxy becomes its own project

Three systems, one concern


The repository as a domain boundary

The domain owns the contract


Modeling payment workflows with rich domain objects

No transition without a precondition