this post was submitted on 01 Sep 2023
338 points (96.2% liked)
Programming
17484 readers
63 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
When writing software that will be deployed to a production environment, it's better to slow down and take the time needed to write a higher quality, more durable solution than to rush and quickly kick a product out the door.
I don't know why this is a hot take, but sometimes it feels like it is.
Even better is to ship small increments often.
Unfortunately in many organisations, leadership doesn't really understand that instead of reducing quality, scope should be reduced in order to ship faster. And developers rarely have a say in these things.
While I agree that it can be considered a hot take industry wide, I don't think for most devs that is a hot take, the ones whom I've seen ship broken stuff were rushed on tight deadlines and didn't have the experience/motivation/political capital to fight back on deadlines.
It's a hot take because managers won't let us :'(