From Donald Knuth & Sir Tony Hoare:
Computer Programming as an Art (1974)
1974 Turing Award Lecture, Communications of the ACM 17 (12), (December 1974), pp. 667–673
The real problem is that programmers have spent far too much time worrying about efficiency in the wrong places and at the wrong times; premature optimization is the root of all evil (or at least most of it) in programming.p. 671
While I agree with Knuth's parable, I think that too many people have misunderstood it. It does NOT mean that you don't have to concern yourself with efficiencies or doing things the right way. For example, creating tables with NVARCHAR(256) or NUMERIC(18,0) for all the column is a very bad thing. Don't confuse "premature optimization" with meaning that you don't have to concern yourself with doing things the right way.
As I tell people, if premature optimization is the root of all evil, what is the result of "no optimization"?
We all know the answer to that question. 😉
If it's worth doing, do it right.
is pronounced "ree-bar
" and is a "Modenism
" for R
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.
"Change is inevitable... change for the better is not".
"Dear Lord... I'm a DBA so please give me patience because, if you give me strength, I'm going to need bail money too!"
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)