Back to posts

Published note

Becoming a Cyborg

Working with AI is not just faster coding. The real shift is recursive workflow improvement: small frictions become small tools, and those tools make the next loop easier.

A week ago, I was still treating AI mostly like a smarter search engine. Useful, impressive, occasionally uncanny — but still basically a tool you poked with prompts.

Now it feels more like I’ve grafted a second cognitive system onto my brain.

Not in the science-fiction sense. No neural implants. No glowing eyes. Just a very real shift in how thinking itself happens when you work closely with AI all day.

The moment it clicked for me was watching Matt Pocock demonstrate his “grill me” workflow. Instead of vaguely brainstorming requirements, he had the AI construct a decision tree, then systematically walk through every branch until ambiguity collapsed into concrete actions and finally GitHub issues.

That sounds small until you experience it.

Because suddenly planning isn’t a foggy human process anymore. It becomes executable cognition.

You stop holding half-formed structures in your head. The AI holds them with you.

And I think this is going to completely change software development.

Solo developers are about to become absurdly powerful

Historically, there’s been an enormous amount of friction between:

having an idea

refining the idea

planning the implementation

building supporting tools

wiring systems together

documenting everything

revisiting decisions later

Most of software engineering isn’t raw creativity. It’s translation overhead.

You think something. Then you explain it. Then you rewrite it. Then you structure it. Then you implement it. Then you build tooling around it. Then you automate the tooling. Then you forget why you built it.

AI collapses huge amounts of that overhead.

The important thing is not merely that AI writes code quickly. People are focusing too much on that part.

The real breakthrough is recursive acceleration.

You use AI to build small tools that remove friction. Those tools improve your workflow. The improved workflow lets you build more tools. Those tools remove more friction. And the cycle compounds.

That compounding effect is the story.

Bootstrapping yourself into a new cognitive layer

This reminds me of self-bootstrapping systems in nature.

Once a seed exists, growth accelerates. Once language exists, culture accelerates. Once tools exist, tool-making accelerates.

AI feels like that.

At first you ask it simple questions.

Then you realise it can structure thought. Then you realise it can critique thought. Then you realise it can maintain context better than your exhausted human working memory. Then you realise you can ask it to build the exact tiny utility you always wished existed but never had time to make.

And this is where things get strange.

Because pre-AI, there were hundreds of “nice-to-have” ideas that simply died on contact with reality.

“Useful, but not worth a day.” “Useful, but too annoying.” “Useful, but I can live without it.”

Now those ideas often take minutes.

A script. A visualiser. A parser. A workflow helper. A local tool. A dashboard. A summariser. A naming assistant. A migration utility. A little UX improvement you always wanted.

The cost of experimentation collapses.

And when experimentation becomes cheap, creativity explodes.

The silence after the noise

One of the most surprising effects has nothing to do with code generation.

It’s cognitive clarity.

Traditional software development contains an unbelievable amount of noise:

boilerplate

syntax wrangling

context switching

searching documentation

repetitive plumbing

remembering APIs

managing tiny incidental details

You spend so much energy wrestling the machinery that the actual thinking gets drowned out.

But once AI absorbs a chunk of that noise, the signal starts coming through much more clearly.

You can feel the underlying architecture of ideas again.

You can stay in flow longer. You can explore more branches. You can test intuitions rapidly. You can ask “what if?” repeatedly without paying a massive implementation penalty every time.

And honestly?

It feels wonderful.

Not because the machine is replacing thinking. Because it removes enough friction to let you think properly again.

This is bigger than coding

Right now, most people still frame AI as:

chatbots

search

content generation

coding assistants

But I think the deeper shift is this:

AI becomes part of your cognitive scaffolding.

A collaborator for structuring ambiguity. A memory prosthetic. A systems-thinking amplifier. A friction destroyer.

That changes how individuals operate.

And once enough individuals operate differently, workplaces change too.

Meetings become different. Planning becomes different. Documentation becomes alive instead of dead text. Decision-making becomes traceable. Tiny teams begin competing with large organisations.

The leverage increase is difficult to overstate.

The danger

There is a warning here too.

If you remove friction entirely, you can accelerate nonsense just as efficiently as brilliance.

You still need judgment. Taste matters more than ever. Direction matters more than ever. A bad idea executed at superhuman speed is still a bad idea.

Maybe worse.

The people who thrive won’t simply be the people who can prompt well.

They’ll be the people who can:

identify meaningful signals

ask good questions

maintain coherent direction

design systems instead of just outputs

stay psychologically grounded while operating at much higher cognitive throughput

The AI amplifies what is already there.

Becoming a cyborg

So yes, after a week, I genuinely understand why people describe this experience as becoming a cyborg.

Not because you merge physically with machines.

Because your thinking process becomes hybridized.

Part biological. Part synthetic. Part conversational. Part computational.

You stop working alone.

And once you experience that properly, going back feels a bit like trying to build a house with a spoon after using power tools.