The The Root Of All Evil =LINK=
Download >>> https://urlin.us/2tq58T
The The Root Of All Evil =LINK=
Dawkins has said that the title The Root of All Evil was not his preferred choice, but that Channel 4 had insisted on it to create controversy. The sole concession from the producers on the title was the addition of the question mark. Dawkins has stated that the notion of anything being the root of all evil is ridiculous. Dawkins' book The God Delusion, released in September 2006, goes on to examine the topics raised in the documentary in greater detail. The documentary was rebroadcast on the More4 channel on 25 August 2010 under the title of The God Delusion.
Paul is trying to warn Christians about the danger of having a love for money. He is not saying that having a lot of money is evil, but that loving money is going to motivate various kinds of evils in your life. By evil, Paul is referring to morally reprehensible behavior.
Paul is warning Timothy (and therefore the church in Ephesus) about the love of money, not money itself. Paul says that this love for money is a root of all kinds of evil. The word for root literally refers to the part of a plant that is below ground. Here, Paul uses a figurative extension that refers to the reason or cause of something.
But those who desire to be rich fall into temptation and a snare, and into many foolish and harmful lusts which drown men in destruction and perdition. For the love of money is a root of all kinds of evil, for which some have strayed from the faith in their greediness, and pierced themselves through with many sorrows.
There is no doubt that the grail of efficiency leads to abuse. Programmers waste enormous amounts of time thinking about, or worrying about, the speed of noncritical parts of their programs, and these attempts at efficiency actually have a strong negative impact when debugging and maintenance are considered. We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil.
Not all early optimizations are evil, micro optimizations are evil if done at the wrong time in the development life cycle, as they can negatively affect architecture, can negatively affect initial productivity, can be irrelevant performance wise or even have a detrimental effect at the end of development due to different environment conditions.
In your case, it seems like a little programmer time was already spent, the code was not too complex (a guess from your comment that everyone on the team would be able to understand), and the code is a bit more future proof (being thread safe now, if I understood your description). Sounds like only a little evil. :)
Thus, in general, I think the right approach is to find out what your options are before you start writing code, and consciously choose the best algorithm for your situation. Most importantly, the phrase "premature optimization is the root of all evil" is no excuse for ignorance. Career developers should have a general idea of how much common operations cost; they should know, for example,
Having plenty of knowledge and a personal toolbox enables you to optimize almost effortlessly. Putting a lot of effort into an optimization that might be unnecessary is evil (and I admit to falling into that trap more than once). But when optimization is as easy as picking a set/hashtable instead of an array, or storing a list of numbers in double instead of string, then why not I might be disagreeing with Knuth here, I'm not sure, but I think he was talking about low-level optimization whereas I am talking about high-level optimization.
In 1976 we were still debating the optimal ways of calculating a square root or sorting a large array and Don Knuth's adage was directed at the mistake of focusing on optimizing that sort of low level routine early in the design process rather than focusing on solving the problem and then optimizing localized regions of code.
But in general optimization leads to less readable and less understandable code and s