Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Adopting anything as blind dogma is Expert Beginner territory. See also: DB table normalization.


I basically spent 2 full years removing normalization from our two projects that was originally added because devs followed best practice.

Those 2 years were to do the data migration and of course there were different priorities, if that would be priority we would do it in 1 month, but we liked to spread risk over time.

Reason was of course performance issues and not really needed joins, where normalization didn't bring any benefit.


In an ideal world the data at rest would be normalized and you’d have a view or a derived table or something when needed to make queries fast when necessary.

If you ever find a job in an ideal world, hold on for dear life and please accept my CV for consideration.


> See also: DB table normalization.

Pragmatic approach: generally end up with an average of around 2.72 normalization across all tables.




Consider applying for YC's Winter 2027 batch! Applications are open till November 2.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: