this post was submitted on 02 Mar 2026
125 points (93.7% liked)
Programming
25882 readers
359 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
If only it was just a problem of understanding.
The thing is: Programming isn't primarily about engineering. It's primarily about communication.
That's what allows developers to deliver working software without understanding how a compiler works: they can express ideas in terms of other ideas that already have a well-defined relationship to those technical components that they don't understand.
That's also why generative AI may end up setting us back a couple of decades. If you're using AI to read and write the code, there is very little communicative intent making it through to the other developers. And it's a self-reinforcing problem. There's no use reading AI-generated code to try to understand the author's mental model, because very little of their mental model makes it through to the code.
This is not a technical problem. This is a communication problem. And programmers in general don't seem to be aware of that, which is why it's going to metastasize so viciously.