Agentic Coding

Software development is stratifying into three distinct tiers. Where you land will determine whether you make more money, the same, or far less than today.

I let Claude Code do whatever it wants without asking permission.

Before you spit out your coffee: I keep it in a jail. A container jail.

In my previous post about Claude Code, I talked about using VS Code devcontainers to safely run Claude in “dangerous mode.” That was great for a typical software project. But what about something harder? What about porting a complex hardware-interfacing library from Python to Go, where you need to deeply understand USB protocols, radio registers, and firmware internals?

That’s exactly what I did with gocat – a Go library for controlling the YardStick One sub-GHz RF transceiver. And Claude Code was instrumental in making it happen.

So I’ve been working on this project called client-w-mcp – it’s a leanring project to truly understand how an AI agent works with MCP servers. And I’m exploring Agentic development - with Claude Code.

Why Claude Code?

The first time I used it, Claude just… flowed. It seems to do a lot more by itself to figure things out. I especially like the Task() so that it can go do more than one thing at a time. It would be bad to try to modify code that way, but to write tests or update docs and not have to wait doing one thing at a time… is wonderful.