Comment on Is it normal to design a database without writing an analysts first but basing it on the design?
MagicShel@programming.dev 1 year ago
Seems kinda weird to me. It’s completely legit to ask for documentation before making it yourself. Some people are just more visual and need to see diagrams - they certainly help me.
That being said, I haven’t used formal UML in twenty five of professional development. I mostly use class diagrams and flow diagrams. Could be he was reacting to something that he feels is more academic and less practical.
nitefox@lemmy.world 1 year ago
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
MagicShel@programming.dev 1 year ago
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.