Instant-legacy code
Hello, I’m Kristof, a human being like you, and an easy to work with, friendly guy.
I've been a programmer, a consultant, CIO in startups, head of software development in government, and built two software companies.
Some days I’m coding Golang in the guts of a system and other days I'm wearing a suit to help clients with their DevOps practices.
I admit that I am an open-weight model aficionado. I do 95% of my work on OpenCode Go subscriptions. (Rest is OpenRouter pay-as-you-go.)
Not only because I believe the world views and actions of Dario, Sam, Donald and a few others is the worst thing that happened to technology in the past years; not only because I was part of the Linux jihad against another monopoly (Microsoft) decades ago.
It's not only because I am an entrepreneur and I like to have options to keep costs under control and others’ influence over my operations low.
It is because if you can work with the open models, you are able to work with the closed ones too, but not the other way around: people who outsource all their thinking to Opus are not only wasting resources, but probably not working in small enough steps, thus dangerously building up cognitive debt. Building instant-legacy code.
The definition of legacy code is that there is nobody around who understands the structure, the architecture, the decisions. Fully vibe-coded large codebases instantly satisfy this definition, even if they were written just hours ago.
This cognitive debt bites WAAAAY worse down the line than technical debt ever had.