No, that's productive programmers. Productivity != competence, and I've seen plenty of examples of this first hand. Besides which, that approach is not suited

No, that's productive programmers. Productivity != competence, and I've seen plenty of examples of this first hand. Besides which, that approach is not suited to all aspects of programming. If you think in terms of a utility programmer - someone who just tweaks here and there when others aren't capable - it swings the other way. Being able to get the client to show you how they do things and attacking the problem that way can save an eternity of poking around trying to trace a problem.