this post was submitted on 24 Jul 2023
5 points (100.0% liked)
Programming
17398 readers
94 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 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
That's really what's going on.
Back in the days, people took the time it was necessary to write the software. And managers trusted the engineers to say when it's ready or not.
Nowadays, the software world is managers going "yes we know the database's gonna blow up over the weekend without the query optimizations, but we want to build this new feature before the end of the week. We can deal with the database when it blows up over the weekend, that's why you guys are on-call."
I did not make this up, I've actually heard this. This is why modern software is so fucked up, not because we can't handle the complexity, because reliability and quality just isn't prioritized at all anymore. Gotta dish out new features every day and you're not allowed to work on fixing known critical bugs.
This hits close to home.