AIToday
Large Language ModelsAI Coding AssistantsZenn AI/MLPublished: Oct 5, 2026, 10:00 JST

Not-yet-AI engineers hold the advantage, writes 20-year SE

Not-yet-AI engineers hold the advantage, writes 20-year SE

3 Key Points

  1. What happened

    A systems engineer with over 20 years of experience, who has run more than a dozen projects in the past half year using AI as a partner, published a book arguing that engineers who have not yet adopted AI at work are in the most advantageous position.

  2. Why it matters

    The author says the common experience of AI returning fluent but generic answers — and the conclusion that 'AI is not useful yet' — is actually a problem of instruction quality, which engineers already know how to fix from managing programmers.

  3. What to watch

    The author says the AI tooling landscape (MCP, custom skills, agent loops, harnesses) is optional and short-lived, so the approach hinges on whether engineers can hold onto purpose, judgment, and verification rather than memorizing procedures.

WHO IT HITSThis lands on SEs and programmers who have tried AI tools only casually and stopped, and on engineering managers weighing whether to invest in AI tooling. It suggests their existing requirements-definition and instruction-giving skills — not new tool knowledge — are the asset to deploy first, though the argument is the author's own view rather than a measured result.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, in your inbox every morning.

Context & Analysis

The author's argument draws on a direct analogy to software development: handing a programmer only a rough instruction like 'build this list screen nicely' produces something that does not match your intent — for example, sort order reversed or display behavior for large record counts unconsidered — and that is not the programmer's fault. The same dynamic, the author says, applies to AI. A request to 'make a script to aggregate logs' yields plausible code that does not match the actual log format, lacks the items you wanted aggregated, and ignores library constraints; adding the purpose, environment, and a few sample lines of the log sharply raises the chance the output works as-is. The difference is the amount of information given and the clarity of purpose, not the AI's capability.

The author also places this in a longer engineering tradition. The core of the book is the sequence engineers have long known as waterfall — decide first, then build — and the author considers what is currently called specification-driven development (SDD) to be the same thing. This is not a book about learning new technology; it is about aiming already-held skills at a new counterpart.

The stated reason not to chase MCP, custom skills, agent loops, or harnesses is threefold: those are means, not ends; the AI itself can guide you through the setup when you actually need it; and elaborate setups tend to have short lifespans, whereas basic interactions — conveying purpose, handing over materials, eliciting options, summarizing into documents, having a human verify — carry over across whichever AI or service you use. The stakes, then, hinge on whether the reader treats instruction quality and purpose definition as the bottleneck rather than tool familiarity. The author's own experience running a dozen-plus projects in half a year is the evidence offered; readers whose work involves sensitive data will note the author defers the line between shareable and non-shareable business information to a later chapter.

FAQ
Does the author say I need to learn prompt engineering or specific AI tools?
No. The author states plainly that no prompt-writing skill and no tool memorization is needed, and that chasing 'god prompt' collections or tool names like ChatGPT, Claude, or Copilot can wait. What matters is asking until you understand.
What did the author's example of a vague bug report turn into?
A vague report of 'something is wrong with the screen' became a specific statement: since yesterday's release, only users with a certain permission see the filter button on the list screen not responding; reproduction steps confirmed; no browser dependency; no error log output.

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleAkamai lands $11.6 billion Anthropic AI infrastructure deal