Systems that are cheap to change
Systems don’t fail because they are slow. They fail because they resist change.
I’ve built data platforms where the architecture was sound and the cloud bill was low, but changing anything took weeks of careful reconstruction.
I’ve watched engineers slow down not because they lost skill, but because they absorbed the complexity the organisation couldn’t see.
I write about these patterns.
I’m a platform engineer focused on developer experience and system design. This blog is built the same way: a small system, fully declared, and cheap to change.