this post was submitted on 31 Mar 2026
169 points (99.4% liked)
Programming
26304 readers
1077 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
I'm fully talking out of my ass here, but I feel like a quick "five whys" exercise at any given company would reveal that the real issue is neither engineers nor code, but rather something systemic.
We used to do retrospectives at one of my old jobs, because everywhere loves cargo-culting agile and scrum stuff.
I quickly realized that a lot of the problems were largely outside the team's control. It was shit like "The CEO doesn't believe in designers or UX, so he won't hire one, so we spend a lot of time doing that work badly ourselves." Or, "management is making us spend all this time in 'planning meetings' so we don't get anything done"
Stuff that has easy solutions, but we can't do because some idiot or powerful cry-baby is in the way.
It’s usually because the engineers were rushed to deliver completely new features because the sales department over promised again.
Dysfunctional engineering teams, that have no empathy for end users is an issue as well.
It is almost always that.
Conway's Law