this post was submitted on 05 Aug 2023
14 points (85.0% liked)
Programming
17424 readers
27 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
The DB is already made, but they had to change it cause they didn't plan a huge portion of its logic beforehand even though they knew about it. This resulted in major changes across the whole schema, while we were already working on implementing the various features
I see. So it’s an absolute cluster fuck because no one did the correct planning in the first place and everyone is flying by the seat of their pants. I don't have a lot of information to go on, but this seems like poor leadership. And you know that because they had the requirements but didn't create the right schema in the first place.
This (whether by leadership failure or honest mistake) is sometimes a reality in software development. And it sucks because that usually puts a lot of pressure on developers to hit moving targets because the deadlines don't usually change just because you spent weeks working on bad design.