I agree with your thinking as well. Then, could you possibly critique my thoughts too? It seems like you and I think similarly, and I’m curious whether my logic is consistent.
[1]https://www.makonea.com/en-US/casual/the-hardest-part-of-usi...
[1]https://www.makonea.com/en-US/casual/the-hardest-part-of-usi...
> being able to understand code by reading it is different from being able to do that same modeling yourself starting from a blank screen
That is simply Domain Knowledge. In a specific context, be it a Framework or an App or a Platform or Infrastructure or whatever else, you have to understand it. Of course, if you start from zero and you build it from scratch yourself, you have pretty much the best DK you can have.
That is usually not the case though. If you have external collaborators of any kind, your DK is always challenged. I find myself often dumped into Domains from which I have to gather Knowledge to understand. And, for me personally, having to read code written by an AI, especially now that they've gotten smart enough to not make glaringly stupid errors, is MUCH better than having to read Hand Crafted Code that has been handslopped (yes, I'm going to coin that term now) to meet Deadlines. Shortcuts, hacks, you name it. Terrible codebase sins, accumulated as years, even DECADES of "we'll fix it later".
Of course it's a pain. It always has been. Back in the GPT 4 / Claude 4 days, AI generated code was atrocious, but that is not the case anymore.
The rest of the article, especially these bolded points:
> The weight shifts from the ability to produce directly to the ability to evaluate output and set direction.
> So in the AI era, productivity is increasingly limited by the speed of judgment rather than the speed of writing.
> A manager who steps away from the front line may, over time, lose the ability to perform the work they are managing.
> does being able to evaluate code mean the same thing as owning the mental model of that program?
Are SPOT ON. You can vibeslop anything at the speed of light. But if you don't have the knowledge, taste, and expertise to not lose track of your DK so that it doesn't become an unmanageable mess, it's going to bite you in the proverbial ass.
But, again, that has always been true!
How is the code that was vibeslopped by ChatGPT in 1 minute different from the Junior Dev who spent a week handslopping a new type of wheel? The only difference is quality and speed.
And you need expertise to be able to recognize when something is wrong, and keep your DK updated at scale.
I also think ‘domain knowledge’ is incredibly important. Whether you write code or not matters, and coding as a hobby is good, but now every company forces you to write code with AI, so you can’t avoid using it, and I find myself thinking about how to maintain my own instincts.
I feel good seeing thoughts similar to mine. I upvoted you, and have a great day.
I can safely say, especially with how close to actual perfection Claude Opus 5.5 is, that it's no longer the case.
Also people generally hate change. The ethical concerns around AI are also understandable and I agree with the vast majority of them, but the vast majority of the "AI BAD" crowd are simply irrationally angry at it and completely unwilling to engage with it in any kind of good faith.
They'll come around. I'm starting to see some change in the gaming community, which was 200% against any form of AI just a little while ago, and now that they're using it to reverse engineer, decompile, mod and mesh together old games there is a lot of people starting to say "Yeah AI is bad, but...".
There is some CRAZY stuff being being worked on which are objectively good for society as a whole which would have you sound insane just last year, and it's only going to get crazier with each new model.
That era is also today. And AI bros were lying to us two years ago, telling us how good the AI was at programming then. "But AI is actually good now" is a take with zero credibility any more, because it's been delivered inaccurately so much.