Full-stack engineering in Python, Erlang and Angular, written by hand for years. Now Claude Code and a few narrow sub-agents write the code. I write the spec and read every diff, so the typing went down and the responsibility didn’t.
As an AI engineer and full-stack developer in Gothenburg I build SaaS products, internal tools, e-commerce sites, plugins and AI agents, plus the integrations and automation that connect them, which is where most of the bugs live.
The same engineer both ways: what I build on my own, and how I build with agents.
Full-stack software, written by hand. It is the foundation the agents work on top of, and the reason I can tell when one of them is wrong.
Since the first GPT-3.5 experiments I have gone from asking for small functions to leaving the coding to agents, with control.
Most projects fall into one of these. If yours doesn’t, tell me what it is and I’ll say honestly whether I’m the right person, including when the answer is no.
Products with accounts, roles, billing and an admin side. Tested, and deployed with a rollback plan, because optimism is not a deployment strategy.
Admin panels, back offices, dashboards and workflow tools: the kind of thing that replaces a spreadsheet nobody dares to touch.
Stores, themes, checkouts and migrations on any platform, plus the systems around them. It has its own page, because there is a lot of it.
Shopify apps, WordPress and WooCommerce plugins, Magento modules: the custom piece your platform forgot to ship.
Tool-using agents with scoped access, evals and a human in the loop, and the human reads the logs. MCP servers let them work with stores, CRMs and databases without being handed the keys to everything.
Integrations and automation, APIs and back ends, command-line tools, data pipelines, and the one-off script that saves a week of manual work and is never mentioned again.
A few things I’ve built or run.
Agents write the first draft. I own the spec, the architecture and the review.
I use Claude Code with a few narrow sub-agents: a builder, a reviewer, an integrator. Each gets only the tools it needs, and none of them gets production. Below is an example of how I set them up, from the house rules to an eval log. The questions and answers cover the same ground in short.
Notes and write-ups. All articles
Each has its own page, laid out the way that kind of work is done.
Tell me what you’re building.