.@EccentricFlower if they could tell you exactly & in some lucid form what they're trying to do, they'd have written the code to begin with.

And we then had the usual unproductive back-and-forth that Twitter limits us to, but I'm going to try a little more in depth here.

Our job as coders isn't translating human into computer. Or, if it is, that's a very small part of it. Our job is to clarify what people think the problem is, and then once we can express it, to type that in in a language that the computer understands.

Disentangling people from their fuzzy thinking, drawing out of them what problem they're really trying to solve, that's what we do. Without us trying to draw out that clarity of thought, we get the exchange that we've all had:

"It's broken."

"Tell me exactly what the error message says."

"It says it didn't work."

You can talk all you want about great communicators, and I'll grant you that there are a lot of people who are very good at manipulating humans into outcomes that meet business needs and enhance shareholder value, but if people can think logically and clearly and procedurally enough to articulate to us what the problem really is, then... well... then programming is just typing.

Trying to understand what people are trying to tell us, trying to get them to clarify their thoughts so that they're actually telling us what the problem is? That's programming.