I can't disagree with that nonsense enough. When he refers to polish, he is referring to code which he has already thought out which will eventually not be repetitive, so applying DRY is easily dismissed as not applicable in that instance. Applying DRY never usually means that you will create branches, etc. You do that if you are writing modular code. The whole point in DRY is that you do not repeat yourself. Good OO DRY code never commonly suffers the need to do what he is describing.
Writing DRY code is actually faster than copying and pasting whole chunks but only if you have a very good understanding of the code. A good reason I can see to not use DRY techniques is if you do not have the skill level required to write DRY code because you are unfamiliar with an included library of classes for instance.
As far as scrubs, he's referring to someone as doing a job which he thinks he is above when it would benefit his project if there where many eyes on the same thing instead. If he understood his libs and tools well enough, he wouldn't need a "Scrub." What use would they be anyway if they are new to the language? How are they going to spot that cross site scripting hole you've copied and pasted five times everywhere? Most people doing the job which he describes make a poor effort because it is well known that developers who are not adding new features are largely disinterested in their work.
My point is that if you learn properly how to write DRY code, you avoid large fixes that involve searching through the entire code for particular strings. If you use OO DRY techniques, your fixes are in one place and are made quickly. There is nothing slow about writing DRY code and very few real disadvantages (None of which he has pointed out.) So if you learn to write DRY code properly you should see your development time slashed by sometimes by as much as three quarters. You will also have considerably less code to maintain.
It's nothing personal. My experience tells me that he is yet to use DRY techniques correctly and if he needs a "Scrub," to tighten up the code, it is almost always faster to just re-write the entire project using DRY techniques instead. If you write code and then try to make it DRY, you have completely misunderstood the point of DRY.
As far as scrubs, he's referring to someone as doing a job which he thinks he is above when it would benefit his project if there where many eyes on the same thing instead. If he understood his libs and tools well enough, he wouldn't need a "Scrub." What use would they be anyway if they are new to the language? How are they going to spot that cross site scripting hole you've copied and pasted five times everywhere? Most people doing the job which he describes make a poor effort because it is well known that developers who are not adding new features are largely disinterested in their work.
My point is that if you learn properly how to write DRY code, you avoid large fixes that involve searching through the entire code for particular strings. If you use OO DRY techniques, your fixes are in one place and are made quickly. There is nothing slow about writing DRY code and very few real disadvantages (None of which he has pointed out.) So if you learn to write DRY code properly you should see your development time slashed by sometimes by as much as three quarters. You will also have considerably less code to maintain.
It's nothing personal. My experience tells me that he is yet to use DRY techniques correctly and if he needs a "Scrub," to tighten up the code, it is almost always faster to just re-write the entire project using DRY techniques instead. If you write code and then try to make it DRY, you have completely misunderstood the point of DRY.