Programming

17374 readers

379 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 !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

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 nitefox@lemmy.world to c/programming@programming.dev

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

[–] Kissaki@feddit.de 11 points 1 year ago (1 children)

This is such a broad question. It's normal and not normal to do so, it's also normal not to do so.

If it turns out / becomes evident you need a diagram now now's the time to create one. You may push quality even without seeing the value in it. In some places or with some people it may be unwanted.

[–] nitefox@lemmy.world 1 points 1 year ago (1 children)

I'm not the one who designed the DB; it's not a simple DB or project though. The problem is, they """found out""" they had forgotten to implement a very important part and they had to heavily change some parts we had already built upon

[–] hglman@lemmy.ml 1 points 1 year ago

What kind of application is it?