In the Age of Intelligence, Coding Was Never the Hard Part
An assistant named Neura now lives on my website. Open her from any page and ask where to start with AI agents, or which piece explained retrieval. She answers in a few plain sentences and points you to the right posts. She has read everything I have published, all one hundred and fifteen of them, and she keeps the whole archive in mind when she replies.
She came together over about three hours of focused work across a single day, with the World Cup and the US Open on in the background. I am not a developer, and I have never claimed to be. Not one line of the code is mine. I directed Claude Code from my terminal, made every real decision myself, and watched a retrieval-powered product come to life in production on my own site.
My reasons for this build went past content for the newsletter. I wanted a living tool inside my own site, not a static archive. I wanted to build it myself, and to apply knowledge I had been developing over more than eighteen months. Retrieval techniques and vector databases have been recurring topics in Neural Gains Weekly, yet I had never wired them together with my own hands. Explaining a concept and building a system around it are two different skills, and I wanted to close the gap. Neura was the chance to do exactly that, with my own archive as the proving ground. That is the part that pulled me in.
Every Stall Was a Decision I Had Not Made Yet
Before any building, Claude Code got one instruction from me, about how we would work together. I told it plainly, "I need to move slow as this world is newer to me." As new ideas entered the stack, a vector store here, an embedding step there, Claude Code paused to explain each one in plain language before we built on it, teaching me the concepts as we went along. Unfamiliar terms became clear within minutes, and the aha moments came faster than they would have alone.
Directing the build looked less like coding and more like a run of decisions. That shift reaches well beyond me. As of January 2026, roughly nine in ten professional developers reported regularly using at least one AI tool at work, in a JetBrains survey of more than ten thousand of them. Even the people who can write code by hand now lean on AI as a matter of course. The same help has simply reached someone who could not write a line of it. I described what I wanted in plain words, and Claude Code proposed a plan. The first real decision was how much to trust it. Rather than let it build and ship on its own, I connected it to my GitHub repository and had it open a pull request for every change, a proposed set of edits waiting for me to review before anything went live. That was the governance I built in on purpose. Claude Code wrote the code and opened the request. My part was to confirm the details I had asked for were actually there, not to hunt through the code for bugs, and to approve it only once they were.
The bigger decisions came before any code was written, and there was no engineer down the hall to settle them. Some I could not have answered without assistance. When it came time to pick where the whole thing would run, I did not know enough to choose between Cloudflare and Google Cloud on my own, so I asked. Claude Code laid out the tradeoffs, one vendor with everything I needed in a single free tier against a more powerful platform built for enterprise scale I did not have. The facts made the call obvious, and the call was still mine to make. The smaller, cheaper model was smart enough for the job, so the expensive option came off the table. Full retrieval beat a quick shortcut, so the archive could grow without boxing her in later. Claude Code wrote the code behind every one of those decisions, but the deciding was the real work, and it was mine.
While building the vector database in Cloudflare, I loaded all one hundred and fifteen posts so Neura could search them, and the terminal work began. This was a new rhythm of commands, so I ran them one at a time and watched what came back. On one of them, nothing happened. Nothing happened, just the command sitting there waiting on me. The cause turned out to be a single missing quotation mark. I worked out why, fixed it, and the posts flowed in. I checked my footing as I went, asking Claude "Did the terminal work?" and "We good?" until the output told me we were. Each command that landed made the next one feel less foreign.
The deployment had noticeable bugs that were only apparent after Neura went live on the site. The chat button hid behind another button where no visitor would find it. Dark text rendered on a dark background, making the header unreadable. And the early answers ran long, stuffed with citation numbers that pointed nowhere. I caught each one the way a reader would have, live on the page, and fixed them in minutes.
A year ago, stalls like these would have overwhelmed me. This time they did not. I stayed calm, worked each one methodically, and knew the next step to take, even without being able to read a line of the code. That steadiness was the surprise. I kept expecting the technical difficulty to be the holdup. It almost never was. Each stall traced back to a decision about what I wanted that I had not yet made. The moment I got clear on the goal, the work moved again quickly. The thing slowing me down had been sitting on my side of the screen the whole time. By the end, I honestly felt comfortable. That comfort was earned, the sum of every rep that came before, going back to my first AI coding project. What I did not expect was how much the job itself had changed underneath me.
A Senior Developer Who Cannot Read Your Mind
In an earlier issue, I treated an AI coding tool like a senior engineer who already knew everything, and I broke my own homepage in the process. The lesson was simple and humbling. I could not hand over the responsibility and step away. What I had then was a junior developer, capable but green, and nothing it produced could go unchecked.
Building Neura, that same kind of tool no longer behaved like a junior. Claude Code, now running on Opus 4.8, reasons through tradeoffs, raises problems before they surface, and explains its choices as it makes them. It feels like a senior dev. The constant supervision the homepage demanded was mostly gone.
It would be easy to read that as the human mattering less in the build. That is not how it played out. As the tool took on more, the weight of the work shifted onto me. A senior developer who cannot read your mind is powerful and a little dangerous at the same time. Hand a vague request to a capable engineer and you get exactly what you asked for, done well and done fast, even when what you asked for was wrong. The sharper the tool gets at execution, the more your half of the job narrows to deciding precisely what to execute. Speed only makes a bad decision arrive sooner.
None of this belongs to one project or one tool. The more capable the machine becomes, the more the work depends on a clear head and a well-chosen problem, which is to say it depends on you. That is the shift worth carrying into whatever you decide to build next.
The Part No Tool Will Ever Do For You
So what is left for you, the capable professional who has been watching all of this from a distance? The most important part, and it is not close. You decide which problem is worth solving and which tradeoffs you will accept. You define what good looks like, and you choose when something is finished. Taste and judgment are yours to supply. They always have been.
The growing ease of these tools does not worry me, because the skill that carried me through this build was a different kind entirely, learning to translate between the problem in my head and the language a machine needs to act on it. That translation holds up far beyond a terminal, in any room where someone has to turn a fuzzy goal into a clear instruction.
So here is the one move worth making this week. Take a single problem that nags at you, the kind of small, recurring friction you have learned to tolerate, and describe it in plain English, the way you would explain it to a colleague. Then open Claude Code, or another tool like it, and start. There is no product to ship here, only your first real rep at directing a machine to build something, which is quickly becoming one of the most useful things a person can know how to do.
Open Neura if you want to see where a few spare hours can land, though the tool itself is beside the point. What matters is this: the starting line is not a coding course, and it never was. You do not need to learn to code. You need to decide what to build, and then decide to begin. That decision was always the hard part. It was just hiding behind the code.