Increasingly, I use coding agents instead of writing software. For example, I built a Blog UMAP. Then, I built Calvin UMAP. And more. But instead of building re-usable software, I just ran Claude with prior context.
Increasingly, I use coding agents to run software. For example, I use Codex to classify my expense receipts. It writes re-usable code, but I run it using Codex, and it updates the code with new/edge cases.
I see a future where coding agents are the wrapper around all software. (Lots of people have spoken about this. I am feeling it now.)
If that’s so, then:
- Agents are the new users of software. We need agent-friendly CLI, agentic web accessibility, and stuff like that.
- Agents ARE the new software. I mean, all sofware is just one coding agent. “Tell the agent to do it”. It’ll find & install what’s required or write it - to get the job done.
If agents are a genie we can’t push back into the bottle, I guess we’ll see more (naive) usage, meaning:
- More one-off uses, e.g. personal use tools & projects (which is great! That’s like Excel templates and macros.)
- More prototypes that are NOT production-ready, leading to Vibe Code Fixer and AI Slop Fixer roles. Also:
- AI Policy Architects (project managers)
- AI Architects
- AI Designers
- AI PromptOps Engineers (developers)
- AI Auditors (testers)
- AI Security Experts
Wait-a-sec… that’s just the usual software roles, but with “AI” in the title, doing slightly different things.
Huh.
