There is something strangely familiar about the way we are talking about artificial intelligence.
Everywhere I go, people are discussing AI.
They are discussing models, agents, benchmarks, reasoning, multimodal systems, autonomous coding, productivity, disruption, alignment, regulation, jobs, and the coming transformation of society.
They are curious. They are excited. They are sometimes frightened.
But after listening for a while, I keep wanting to ask a very simple question:
What did you actually make it do?
This isn’t a criticism of curiosity. Curiosity is where technology begins.
But technology does not transform work because people talk enthusiastically about its possibilities. It transforms work when somebody takes the machine and gives it a job.
I Have Seen This Movie Before
The personal computer went through something similar.
The arrival of the IBM PC, the XT, the AT, the 386 and the 486 was astonishing. Each generation brought dramatically more computing power, more storage, better software and new possibilities.
People talked about what computers would eventually be capable of doing.
And they were right.
But none of that mattered to the bookkeeper sitting at a desk with a pencil, ledger and adding machine.
The important question for that bookkeeper wasn’t:
“How powerful is this computer?”
It was:
“Can this thing make my work easier?”
The breakthrough came when the answer became yes.
A spreadsheet wasn’t important because spreadsheets were technologically impressive.
It was important because someone could stop doing arithmetic by hand.
A database wasn’t important because databases were intellectually interesting.
It was important because someone could find a customer record without searching through filing cabinets.
The personal computer became revolutionary when it stopped being an object of fascination and became an appliance of work.
AI Is Still an Object of Fascination
Much of the current AI conversation hasn’t reached that stage.
We talk about enormous models.
We talk about context windows.
We talk about agents.
We talk about autonomous software engineers.
We talk about artificial general intelligence.
We talk about whether AI will replace programmers, lawyers, teachers, doctors, analysts and executives.
But there is a danger in endlessly discussing the machine instead of the work.
AI isn’t a profession.
AI isn’t a strategy.
AI isn’t a business plan.
AI is a machine.
Give it a job.
The Real AI Question
Suppose you run a company.
You have somebody spending four hours every morning collecting information from different systems and putting it into a report.
Don’t start by asking which frontier model you should buy.
Ask:
Can the machine do the job?
Give it the files.
Give it the APIs.
Give it the database.
Give it the rules.
Give it a test dataset.
Give it access to the tools it actually needs.
Then make it produce the report.
Now you have learned something.
Maybe it works.
Maybe it fails spectacularly.
Either result is more valuable than another meeting about the future of AI.
Because now you have an engineering problem.
And engineering problems can be solved.
The 90 Percent Trap
Modern AI makes this even more interesting because it is often remarkably good at producing the first 90 percent of a solution.
That creates a new temptation.
Someone generates a beautiful report.
Someone generates an application.
Someone generates a deployment script.
Someone generates an analysis.
Everyone looks at it and says:
“Wow.”
But the last ten percent may contain everything that matters.
Is the data correct?
Did the system understand the exception?
Did it preserve the business rule?
Did it introduce a security vulnerability?
Will it work next month?
What happens when the network disappears?
Who notices when it fails?
Who is responsible?
The last ten percent isn’t necessarily more typing.
It is judgment.
And judgment becomes more valuable when production becomes cheap.
This Changes What We Should Hire For
If AI makes competent-looking output abundant, then organizations have to change what they mean by competence.
The valuable employee may not be the person who can produce the most text, code or slides.
It may be the person who can recognize when the machine is wrong.
The person who understands the customer.
The person who knows how the old system actually works.
The person who understands the network.
The person who knows what can safely be automated.
The person who can take an ambiguous problem and turn it into a working system.
The person who can say:
“No. That isn’t the problem we’re actually trying to solve.”
That is not anti-AI.
It is the opposite.
It is recognizing what AI is actually good for.
AI Should Be Given Work, Not Worship
There is a strange social phenomenon developing around AI.
Some people treat AI almost like a new civilization.
Others treat it like a new employee.
Others treat it like a dangerous alien intelligence.
But the most productive relationship may be considerably less dramatic.
Treat it like a very unusual machine.
Give it a task.
Give it tools.
Give it constraints.
Give it data.
Test the result.
Measure the result.
Keep what works.
Throw away what doesn’t.
Then give it another job.
That’s how technology becomes infrastructure.
The Person Who Knows How to Use the Machine Wins
The important worker of the AI era may therefore not be the person who knows the most about AI.
It may be the person who already knows something worth doing.
The network engineer who uses AI to automate infrastructure.
The teacher who uses AI to create individualized exercises.
The mechanic who uses AI to diagnose an intermittent fault.
The accountant who uses AI to reconcile thousands of transactions.
The security engineer who uses AI to examine enormous quantities of logs.
The programmer who uses AI to eliminate the repetitive parts of programming and spend more time thinking about architecture.
These people don’t need to spend their day talking about artificial intelligence.
They need to use it.
The Coming Divide
I suspect the emerging divide won’t simply be between people who have AI and people who don’t.
It will be between people who talk about AI and people who incorporate AI into useful work.
The first group will have opinions about agents.
The second group will have agents doing things.
The first group will debate which model is best.
The second group will have tested three models and know which one works for their particular job.
The first group will discuss productivity.
The second group will have eliminated six hours of repetitive work from their week.
The first group will ask whether AI is going to change their industry.
The second group will already be changing it.
The Computer Didn’t Replace the Bookkeeper
The PC did not simply arrive one morning and eliminate bookkeeping.
It changed the economics and mechanics of bookkeeping.
It automated arithmetic.
It changed record keeping.
It changed reporting.
It changed auditing.
It changed what a competent bookkeeper could accomplish.
Eventually, the person who insisted on doing everything with a pencil and adding machine wasn’t demonstrating craftsmanship.
They were operating outside the technological reality of their profession.
AI may do something similar.
It may not eliminate every profession.
It may instead eliminate enormous amounts of work inside professions.
And that distinction matters.
The future may belong neither to humans alone nor to machines alone.
It may belong to people who know how to construct effective combinations of the two.
So Stop Asking What AI Can Do
That question is becoming almost useless because the answer is becoming enormous.
Ask something smaller.
Ask:
What job should I give it?
Then give it one.
Make it work.
Measure it.
Break it.
Fix it.
Give it another.
Eventually you won’t be talking about AI anymore.
You’ll simply be talking about getting the work done.
And that is probably when the AI revolution will have actually arrived.
Facts Only
* People discuss AI models, agents, benchmarks, reasoning, multimodal systems, autonomous coding, productivity, disruption, alignment, regulation, jobs, and societal transformation.
* The personal computer revolution occurred when computing power, storage, software, and possibilities increased.
* The importance of technology shifted from its impressive capability to whether it made a specific task easier for the user.
* A spreadsheet became important because it automated manual arithmetic, not just because it was technologically advanced.
* A database became important because it enabled finding customer records without manual searching.
* Current AI conversation focuses on models, context windows, agents, autonomous software engineers, and artificial general intelligence.
* The author advises giving the machine a specific job by providing files, APIs, databases, rules, and test datasets before expecting results.
* Modern AI often produces 90 percent of a solution, leaving the final 10 percent involving judgment regarding correctness, exceptions, security, and future viability.
* Valuable employees may shift from producing content (text, code) to recognizing machine errors and understanding context and system integrity.
* The most productive relationship with AI involves treating it as an unusual machine by giving it tasks, tools, constraints, and data.
Executive Summary
The discussion surrounding artificial intelligence is currently dominated by abstract concepts such as models, agents, benchmarks, and the future transformation of society. The author suggests that this fascination with AI lacks substance because it focuses on the machine rather than assigning it a specific task or job within existing workflows. The article draws a parallel to the personal computer revolution, arguing that technological advancement only transforms work when a machine is integrated to make a specific human task easier, moving from an object of fascination to an appliance of work.
The author posits that much of the current AI conversation focuses on large models and potential future scenarios rather than practical implementation. A proposed approach is to treat AI as a machine requiring a job, providing it with necessary context, tools, and constraints. This shifts the focus from discussing what AI *can* do to solving concrete engineering problems. Furthermore, the abundance of superficially good AI output creates a new demand for human judgment—the ability to assess accuracy, understand exceptions, and ensure security—which becomes more valuable when production is cheap.
The conclusion suggests that the valuable role in the AI era will shift toward individuals who can recognize machine limitations, understand context, manage systems, and bridge ambiguous problems into working solutions rather than those who merely talk about the technology.
Full Take
The narrative presents a critique of the current discourse surrounding artificial intelligence, arguing that enthusiasm for potential capabilities overshadows the necessity of practical application and engineering. The core pattern observed is a shift in value: from abstract technical prowess to applied utility and critical judgment. This echoes the historical trajectory of technology adoption, where utility—the ability to reduce friction in existing work—drove revolution more effectively than raw power alone.
The piece deploys a constructive framework for engagement by redirecting attention from speculative debates (e.g., "What will AI replace?") toward operational tasks (e.g., "What job should I give it?"). The potential manipulation lies in allowing the discussion of macro-level concepts to distract from the micro-level necessity of defining actionable, measurable engineering problems. The transition from worshipping the machine to using it as infrastructure is a crucial pivot for human agency.
The structure subtly sets up a dichotomy between theoretical observers and practical implementers. The implication is that cognitive sovereignty in the AI era rests not in understanding the newest model architecture, but in mastering the skill of critical assessment and system orchestration. The demand shifts from knowing *what* AI can do to knowing *how* to reliably direct it, suggesting that true power resides in the human capacity to define meaningful constraints and measure complex outcomes, thereby defining the work itself rather than being defined by the tool.
Bridge Questions: What specific tasks within current professional workflows are most ripe for immediate automation through task assignment? How can organizations structure feedback loops to effectively train the "judgment" layer of human oversight when AI produces competent but flawed outputs? What historical parallels exist where the focus on power over purpose led to technological stagnation?
Sentinel — Human
This text functions as a thoughtful, philosophical essay using historical analogy to argue for a specific framework regarding the integration of AI into work, displaying strong human rhetorical structure.