Programming

17662 readers

240 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

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 [email protected]

founded 2 years ago

MODERATORS

snowe

Ategon

[email protected]

Is it normal to design a database without writing an analysts first but basing it on the design? (lemmy.world)

submitted 1 year ago by [email protected] to c/programming

24 comments fedilink hide all child comments

The other day I asked for an analysis or at least an UML diagram since we are having quite some troubles and my boss looked disgusted at me for asking such a question. I’m not a professional backend developer, so I don’t know how it works professionally

you are viewing a single comment's thread
view the rest of the comments

[–] MagicShel 14 points 1 year ago (1 children)

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.

[–] [email protected] 3 points 1 year ago (1 children)

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 4 points 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.