Software architecture built to survive change
A healthy system is not one that avoids change. It is one that lets you alter an important rule without turning every delivery into an investigation.
Read articleTechnology, engineering, and product
Insidesoftware.
Software explained from the inside — from essential concepts to the decisions that make each system work.
Explore articles
Featured reading
Technical archive
Articles
Architecture, frontend, backend, infrastructure, product, security, and artificial intelligence.
Architecture
Software architecture built to survive change
How to design boundaries, contracts, and observability so software remains easy to change when product, team, and scale stop being predictable.
Frontend
From DNS to the database: anatomy of a web request
Understand DNS, connections, servers, queries, and rendering as measurable parts of one operation — and stop optimizing only where it is easiest to look.
Artificial intelligence
AI agents need clear boundaries
A reliable agent is not one with unrestricted access. It operates through small tools, verifiable context, and limits proportional to the impact of each action.
