54
What we lose when we stop coding
(newsletter.humanwhocodes.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 03 Jun 2026
54 points (100.0% liked)
Programming
27173 readers
269 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 3 years ago
MODERATORS
There have been non-coding software architects for decades before LLMs became a thing. Most of us more experienced people are not in architect positions mainly because there are way fewer of those available. That's changing now.
Non-coding architects has been a well known organizational red-flag for decades.
Non-coding people always lose track of reality, and it's a disaster to give them decision power over fine-grained technical choices.
Now, I don't really know how that maps into non-coding software developers, but I'm not optimist.
It’s a matter of feedback loops.
It’s the same problem as when you divide teams by front-end/back-end, or implementation vs testing, or features vs platforming.
When you don’t have to feel the pain of your decisions, you’re going to make bad decisions.