Why I'm starting a blog in 2026
Starting a blog in 2026 is a little bit old school, and I know it. The writing happens in feeds now — short, fast, and gone by the afternoon. I have tried that, and it turns out the things I actually want to say do not survive the format.
Table of Contents
The old-school part
A post has no algorithm to please. It sits at a URL, it can be long when it needs to be, and it is still there in two years when somebody hits the same problem I did. That is the whole appeal.
There is also a selfish reason. I cannot leave a thing alone until I know why it works, and writing is the cheapest way to find out whether I really do. Most of the opinions I hold loosely fall apart in the second paragraph, which is useful to know before I say them out loud in a meeting.
If I cannot explain a decision in writing, I have not finished making it.
What the international journey keeps teaching me
I build and lead engineering teams across different countries — Zurich, Madrid and a fair amount of time in between — in regulated finance, identity, media and now AI. Different languages, different working cultures, different ideas of what “done” means and how directly you are supposed to say things.
That is the real education, and it is still going. The same technical problem looks genuinely different depending on which chair you are sitting in and which country you are sitting in it — and almost nobody writes about that part, because it does not fit in a diagram.
What I’ll be writing
Three things, roughly. Managing, which is mostly the parts nobody puts in the job description: what I got wrong, what it cost, and how often the technical call and the commercial one turn out to be the same call in different clothes.
Technology, at the level of building it rather than presenting about it — I have earned my opinions on Kubernetes the hard way, and I reach for Rust when I want to stop guessing whether something is correct. And trading, maybe: sizing a position teaches you more about deciding under uncertainty than any planning framework I have been handed, mostly because being wrong there arrives with a price tag.
No frameworks unless I have used them in anger. If something here is useful, argue with me about it — the best version of any of these ideas has come out of a conversation with someone who had seen the same thing from a different angle.
