One of the strongest recommendations for clean and pragmatic development is the DRY-principle:
Don’t Repeat Yourself!
This principle is not only part of every guide about professional development but also the reason why we even have things like subroutines, config files and – hello, database professional – data normalization.
Although normalization should be a well-known practice for database professionals, I caught myself writing the same SQL statements again and again, copy-pasting parts as sub-selects, use it in procedures and functions and ending up at having the same query logic in many different places.
We database people are very strict about redundant data in our database design – why aren’t we as strict about the code we write?