“The horrors of remaining accountable without cognitive ownership”
The vibe coders forget that part of what a software engineer is. When it all goes up in flames Claude isn’t going to own it. If I’m going to be responsible for it I need to work in an environment that gives developers the space to understand what we’re building. The expectation from this industry of having developers just wrangle infinite code generators all day without a second thought for true understanding is pure delusion.
my entire career strategy hangs on a strong belief that we are not going to see fully automated software generation in my lifetime.
but we are going to see an end to the ralph-loop, spec-driven-one-shot-dream, and the "end of white collar work" hype.
we're already seeing some high profile players in software development start to set their coarse along the same path i've been following these past few years. it starts with "wow" then "i can use my skills to fully automate this" and then it proceeds to "fast but no cognitive ownership" then disappointment, confusion, frustration, and ends with "hey, this isn't going to work guys, we need to be more disciplined and look at the code, keep our cognitive ownership, and just use the tools to improve our outcomes. these are not our replacement, these are our accelerators. it's the same story, different tooling".
i'm already there. if a company were to come to me today and say "we tried all the trendy stuff but it just made everything worse, we're losing control of our code base, we need to either ditch these things or make them a power-up" then i am ready for that.
if i am wrong, then so be it. my career is over anyway because i have zero interest in giving up cognitive ownership and responsibility (the ability to respond), while remaining accountable.
i'd rather wash dishes or stack shelves than submit myself to the horrors of remaining accountable without cognitive ownership, agency, and responsibility.