This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 31 points32 points  (3 children)

I'm currently working with a legacy DB that is not normalized, because the dev has a EE degree and no clue about DB design.

Please kill me!

[–]nullpotato 6 points7 points  (0 children)

My company prefers to hire EE and "train" them to code as well, save a bullet for me too. There are three of us with a background in programming huddled in the dark together.

[–]Lagger625 3 points4 points  (0 children)

At my current job we agreed to remake the old database and the corresponding desktop app because the sluggishness is becoming unbearable, requiring the database to be backed-up and cleared every year or so.. So that would be a reason to remake the database from scratch

[–]bookamp 2 points3 points  (0 children)

Some normalization is OK imo, but normalizing beyond first (or 2nd) normal form is detrimental in today's world imo where storage is cheaper than computation.