No, and it's a bit frustrating when several people explain in great detail the components of a programming day and how they combine and what the combination tendency is and then someone comes back with the same "but mah productivity". It's also typical for a certain mindset, of course.

Anyway, a counter-example is that the arguments above would not be against some broad framework that reduces both the thinking and the writing needed to construct programs - say a combination of a good programming, a good software engineering framework and a management that forced client requirements into a structured format. That sort of thing can reduce the needed programmer activity in a project on both the low and the high level and none of the arguments above object to this.