3 ms·
> but few … nay, none who could tell me what the properly normalized data model was I guess we have an entire generation of software engineers who never had t
by PheonixPharts 3y ago
> but few … nay, none who could tell me what the properly normalized data model was
I guess we have an entire generation of software engineers who never had to cram the degrees of normal forms for an exam? [0] The term "Boyce-Codd Normal Form" is etched in my neurons.
For anyone who seriously studied relational databases the normal forms are very clearly defined. This is not some "unknown" used to justify arbitrary design.
Likewise anyone who has seriously worked at delivering data at scale in an efficient way has consciously considered the trade-offs between normal and de-normalized data.
Furthermore the reason for Normalization isn't because it's pretty, but because it can drastically reduce the complexity of updates when you have duplicated, but mutable, data as well as reduce overall storage space back in an era when that was a major issue.
0. https://en.wikipedia.org/wiki/Database_normalization#Normal_forms https://en.wikipedia.org/wiki/Database_normalization#Normal_...
- richiebful1 3y ago"Database Management" was an elective in my Bachelors in Computer Science program (Class of 2018). That's the only time we discussed normalization, iirc.
- deathanatos 3y ago> etched in my neurons Along with "The key, the whole key, and nothing but the key, so help me Codd."
- xboxnolifes 3y agoI don't know about an entire generation. A database class which was mostly about normalization and relational algebra was a requirement for my degree, and I graduated fairly recently. I wouldn't be able to recall every form and their requirements, but the general principles are etched into my thinking. It's almost "common sense" to structure data in BCNF, even if one doesn't recognize it as such.