Locklin's basic point is about the important of thinking about the actual problem, instead of playing with tools further removed from the problem. And I can't a

Locklin's basic point is about the important of thinking about the actual problem, instead of playing with tools further removed from the problem. And I can't agree more. The same applies to programming, and applies more and more as we get further removed from the essential problem and the underlying system. It used to be common (appalling but common) to see knowledgeable, experienced programmers give up on trying to understand a system, and to start a cycle of just-change-something, recompile, test... Eventually they'd come up with something that would pass the test and declare the bug "fixed" (for now). Times change. Now we've got stackoverflow and copilot ... so we've got thousands (millions) of kiddies who have little concern for the problem or the system, because they focus on plugging in some code snippet. And the odds of those snippets being inappropriate, or adding further bugs, is overwhelmingly high. We should all be concentrating on understanding the situation and the problem, not on producing any old answer or on passing a test suite.