I actually don’t need to know how my IDE works to use it.
Neither do I need to know how a transformer works to use an AI agent. What does that have to do with anything?
I need to know Java to recognize whether IntelliJ’s refactoring produced sensible Java, just as I need domain expertise to recognize whether an AI agent produced sensible output. “Requires oversight and expertise” does not mean “requires understanding the internal implementation of the tool.”
With increasing degrees of specificity, it kind of is, yeah.
No, it really isn’t, and this is probably the strangest part of your argument.
Specificity of requirements and effort of implementation are two completely different things.
“Take these 30 classes, rename this field, update its usages, add null checks at these boundaries, update the affected tests, and run the test suite” is a reasonably specific description of a task. It is quite obviously not equivalent in effort to manually performing every edit.
“Create a sequence diagram showing the interaction between these five services for this request flow” can take seconds to describe and considerably longer to manually construct.
“Take these documents, extract these specific metrics, compare them by quarter, and put the results into a PowerPoint using this existing deck as the visual template” is a perfectly comprehensible specification. Actually reading the documents, extracting the data, calculating the comparisons, creating the charts and assembling the slides is where the work is.
This distinction is the entire reason programming exists. A specification describes what computation you want performed. We don’t conclude that because SQL lets me precisely specify which data I want from a database, I might as well manually inspect every row.
And “it only saves time where you don’t care about shit-quality work” is just begging the question. You’ve defined AI output as shit and then concluded that anyone accepting AI output must therefore not care about quality.
The useful workflow isn’t “ask AI for something and blindly ship whatever comes out.” It’s “specify the task, let the machine perform the expensive mechanical portion, inspect the result, and correct or reject it where necessary.”
Sometimes that is slower than doing it yourself. Sometimes the output is shit. Sometimes AI is simply the wrong tool.
But the idea that describing a task with sufficient precision inevitably approaches the effort required to execute that task is just demonstrably false.
If that were true, half of software engineering wouldn’t exist.