Technocracy, in its old sense, meant a simple trade: hand decisions to whoever can show the numbers. Trust the model, trust the metric, let the dashboard decide. There's something genuinely good in that impulse — I'd rather argue about what the data says than about who shouts loudest.
But I've spent long enough building and running systems — cloud platforms, migrations, the occasional 3 a.m. incident — to know that the numbers are never the whole story. Every architecture diagram I've ever shipped was eventually bent, broken, or quietly saved by something no spreadsheet predicted: a tired teammate who caught the edge case anyway, a customer who refused to behave like the persona doc said they would, a call made on a hunch that turned out to be right for reasons nobody could fully articulate.
That's the "modern" part. Not less rigor — more honesty about where rigor runs out.
This blog is where I'll write about both halves of that sentence: the engineering (cloud architecture, the tradeoffs behind the tools, notes from organizing Global Azure Poland) and the parts of the job that resist being turned into a metric — judgment, timing, the read of a room.
If you're here for clean answers, you'll mostly find well-reasoned ones instead. That's the deal.