
The Skill of Not Building in the AI Agent Era (5) — Six Checks to Run Before You Start
Will that code still be needed once the next model ships? Six things worth checking before you start.
Alopex Family
Asopitech Labo
Enterprise plans

Will that code still be needed once the next model ships? Six things worth checking before you start.

Homegrown long-term memory, a workflow DSL, a model router. Each one works, and each is genuinely interesting to build. But what if three months of waiting made them unnecessary?

Boris Cherny, who built Claude Code, says he hasn't hand-written a line of code in eight months. Is the craft of polishing prompts giving way to the craft of designing loops?

The code runs and the tests pass. Only the value of using it has vanished. A look at this failure mode as a stranded asset rather than technical debt.

PDF chat, AI slides, ChatGPT plugins: all standard features of ChatGPT and Gemini now. Where did the implementations that once powered them go?

In the US, an "IT company" means Microsoft or NVIDIA; in Japan, it means NTT Data or Fujitsu. The same words point to different things. One side mass-produces products for the world; the other supports each customer's bespoke operations. That structural gap has split revenue, talent, and competitiveness. How does generative AI reshape it? A look from Japan's weaknesses and strengths.

Coding agents are strong at logic and tests. But they can't tell what a piece of data means, who owns it, how fresh it flows, or which copy is authoritative. It follows from the fact that today's AI has no embodiment: the people who rise in value are those who can design the meaning, quality, lineage, and responsibility of data. A look at the trend with the latest data-engineering discussion.

The finale. The core skill common to every part is turning experience into a form both people and AI can act on. Why it does not commoditize and instead compounds, the daily practices, and even "what if AI gains a body?"—the synthesis goes deep.

Break work down, share expectations and criteria, give feedback. The template of good management overlaps exactly with good instructions to an AI team. How the experience of leading AI grows leaders and managers, and how it turns the organization's learning loop.

The key for intermediates who stall at "I basically get it" is to teach AI. Verbalizing your premises, constraints, criteria, and edge cases becomes training that turns tacit knowledge into explicit knowledge. A learning method that uses AI as a mirror of your understanding, plus a practical five-step routine.

In an era where AI hands you answers, are beginners at a disadvantage? Quite the opposite. By trying sticky material—dev environments, containers, VMs—together with AI and failing together, beginners build experience the fastest through iteration. Includes how to let AI fail a lot and learn by watching. Part 2.

Many people worry that AI will take their jobs. But reframing the question opens a path forward. As the introduction to a five-part series, this piece maps out AI-era careers across the beginner, intermediate, and leader stages.
Will that code still be needed once the next model ships? Six things worth checking before you start.
Homegrown long-term memory, a workflow DSL, a model router. Each one works, and each is genuinely interesting to build. But what if three months of waiting made them unnecessary?
Boris Cherny, who built Claude Code, says he hasn't hand-written a line of code in eight months. Is the craft of polishing prompts giving way to the craft of designing loops?
The code runs and the tests pass. Only the value of using it has vanished. A look at this failure mode as a stranded asset rather than technical debt.
PDF chat, AI slides, ChatGPT plugins: all standard features of ChatGPT and Gemini now. Where did the implementations that once powered them go?
In the US, an "IT company" means Microsoft or NVIDIA; in Japan, it means NTT Data or Fujitsu. The same words point to different things. One side mass-produces products for the world; the other supports each customer's bespoke operations. That structural gap has split revenue, talent, and competitiveness. How does generative AI reshape it? A look from Japan's weaknesses and strengths.
Coding agents are strong at logic and tests. But they can't tell what a piece of data means, who owns it, how fresh it flows, or which copy is authoritative. It follows from the fact that today's AI has no embodiment: the people who rise in value are those who can design the meaning, quality, lineage, and responsibility of data. A look at the trend with the latest data-engineering discussion.
The finale. The core skill common to every part is turning experience into a form both people and AI can act on. Why it does not commoditize and instead compounds, the daily practices, and even "what if AI gains a body?"—the synthesis goes deep.
Break work down, share expectations and criteria, give feedback. The template of good management overlaps exactly with good instructions to an AI team. How the experience of leading AI grows leaders and managers, and how it turns the organization's learning loop.
The key for intermediates who stall at "I basically get it" is to teach AI. Verbalizing your premises, constraints, criteria, and edge cases becomes training that turns tacit knowledge into explicit knowledge. A learning method that uses AI as a mirror of your understanding, plus a practical five-step routine.
In an era where AI hands you answers, are beginners at a disadvantage? Quite the opposite. By trying sticky material—dev environments, containers, VMs—together with AI and failing together, beginners build experience the fastest through iteration. Includes how to let AI fail a lot and learn by watching. Part 2.
Many people worry that AI will take their jobs. But reframing the question opens a path forward. As the introduction to a five-part series, this piece maps out AI-era careers across the beginner, intermediate, and leader stages.