If we wish to count lines of code, we should not regard them as "lines produced" but as "lines spent."

Yes, I share your concern: how to program well -though a teachable topic- is hardly taught. The situation is similar to that in mathematics, where the explicit curriculum is confined to mathematical results; how to do mathematics is something the student must absorb by osmosis, so to speak. One reason for preferring symbol-manipulating, calculating arguments is that their design is much better teachable than the design of verbal/pictorial arguments. Large-scale introduction of courses on such calculational methodology, however, would encounter unsurmoutable political problems.

A programming language is a tool that has profound influence on our thinking habits.

Experience does by no means automatically leads to wisdom and understanding.

Elegance is not a dispensable luxury but a factor that decides between success and failure.

Production speed is severely slowed down if one works with half-time people who have other obligations as well. This is at least a factor of four; probably it is worse.

Computer science has as much to do with computers as astronomy has to do with telescopes.