Most technology writing is too careful

Most technology writing is too careful.

It hedges. It lists six options and refuses to pick one. It is written to be impossible to disagree with, which makes it impossible to learn anything from. You read a thousand words and come away knowing exactly what the author thinks: nothing.

I want to do the opposite here.

I am a CTO. I build systems, I run teams, and I am accountable when things break. That seat gives you opinions, because you live with the consequences of being wrong. This site is where I write those opinions down.

A few things I will try to hold myself to.

Pick a side. If I have a view, I will state it in the first line and defend it. You should be able to disagree with me clearly. That is the point.

Stay concrete. Real examples, real numbers, real tradeoffs. Abstractions are where bad arguments hide.

No hype. I am not here to tell you something is going to change everything. When I am genuinely excited about a thing, it will show in the detail, not in the volume.

Earn it. Strong opinions are cheap. Strong opinions backed by having actually done the work are worth reading. I will aim for the second kind.

The topics will mostly be the things I spend my days on: AI in engineering, system design, automation, the web, cloud, and the parts of crypto that are about building rather than betting.

These are my views, not my employer’s. If you take something useful from them, good. If you think I am wrong, even better - that is the conversation worth having.

More soon.