You can describe what the input and output of a function should be, but unless you can describe the mechanism by which one turns into the other, you aren't comm

You can describe what the input and output of a function should be, but unless you can describe the mechanism by which one turns into the other, you aren't communicating what code does. This is the disconnect between programmers and non-programmers; people operate at a level of abstraction that is fundamentally incompatible with computer software. Programming skill is about learning how to think about an abstract concept and realize it as a discrete concept, and try as we might we've been unable to come up with a way to get computers to intuit what we really mean when we speak in nonspecific terms. "Writing down code" is, perhaps, plebian work. Understanding a problem as expressed by humans and being able to connect that to the code to write, though, is where the real work is. Based on my experiences with ChatGPT and Copilot, AI isn't there yet. It's good at the plebian work, which is great, but it's hot garbage at the actually difficult thing.