50
How good engineers write bad code at big companies
(www.seangoedecke.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 30 Nov 2025
50 points (96.3% liked)
Programming
25506 readers
285 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
I'm not sure why the author chose this sentence and why you are picking it out. The author provided no evidence of it. Instead, when you read on it seems to be an ownership problem. People rotating in and out for a year on a ten year project. You can be the most competent and skilled worker, if you don't get the opportunity to become invested in the success of a project, of course you won't see the project become successful.
They're contextualizing and sourcing it plenty. It's their impression from their experience, from their years of being in that field. In the later adding of comments at the end they go into different takes as well, reiterating that it's what they saw or see in [their] big corp[s] [and those he talks to].