The code is AI’s.
The responsibility is mine.
I’m Casper, a software engineer by trade, freelancing in Copenhagen after 10+ years of writing code by hand. Today AI agents write the code, and they’re steered by that experience. I review every change and take responsibility for what ships.
How I work
An example project, simplified. I don’t just build what’s asked, I push back where it matters. You’re the reviewer: nothing moves on without your sign-off.
We start with the problem, not the wish list. I ask the questions that turn a good idea into a better one.
We need a booking system. Right now it’s a spreadsheet and a lot of phone calls.
Transcribed the kickoff call → 12 requirements, 5 open questions.
Most of those calls are people moving a booking. What if they could just do that themselves?
pushbackThat would take away half our calls.
I decide the architecture, and suggest what you didn’t think to ask for. Agents stress-test it first.
Could it send reminders by text, too?
Yes, and let people reply “move” to pick a new time. Reminders that cut no-shows, not just nag.
even betterStress-tested 3 setups for 200 bookings a minute and text replies.
The simplest one holds up, and fits the team that will own it. Going with that.
Agents write the first draft. I review every line, and push it further than the brief.
Opened PR #14: booking calendar — 23 tests passing.
Two people booking at once can get the same slot. Block that, and prove it with a test.
caught itAnd when a slot is full, offer a waitlist. Cancellations fill themselves.
ideaDone. 26 tests passing, waitlist included.
You get a clean codebase, current docs, full ownership, and a few ideas for what’s next.
Wrote the README, architecture notes and an onboarding guide.
Repo, hosting and keys are in your accounts. Walked your team through all of it.
For later: bookings straight from Google Maps. It’s on your roadmap, not your bill.
nextGreat, we can take it from here.
Shipped.
Four steps, four signatures. The agents did most of the typing — every decision still had a human name on it.
Why not just vibe code it?
Vibe coding gets you a demo. My clients need software that still works in a year. The AI is the same; the difference is the engineer in control.
| Vibe coding | Code by Panduro | |
|---|---|---|
| Architecture | Whatever the model picks, one prompt at a time. | Decided by me up front, from the data model out. |
| Code review | If it runs, it ships. | I read every change before it is merged. |
| Tests | Rarely, and never for the edge cases. | Written with every feature, run on every change. |
| Security & data | Hoped for. | Checked by someone who knows where things break. |
| In a year | Nobody understands it, so it gets rewritten. | A codebase your team can read, own and extend. |
After launch, the agents keep working.
Your software doesn’t go quiet when the project ends. Agents watch it day and night, and every change they propose comes past me before it reaches you.
Agent · Securityon watch
Safe
Code and dependencies are scanned for vulnerabilities around the clock. Fixes arrive as reviewed pull requests, not surprises.
Agent · Upkeepon watch
Up to date
Frameworks, packages and runtimes are kept current in small, tested steps — no big-bang upgrade every three years.
Agent · Improveon watch
State of the art
As the tools get better, so does your software. New patterns and performance wins are proposed as they appear.
Selected work
- Affiliate Tracker — Knowing which click actually paid off.
- Agent Harness — The control room where my agents work — and wait for my sign-off.
- JC Nordic — From copying orders by hand to a webshop of their own.
- Adlab — Change an offer once. Every website follows.
- Senzone — Film your walk. Get the right insoles.
- Villy Jensen — A webshop that always knows what’s on the shelf.
- Snevagten — Snow cleared at 4 am, and customers can see it.
- Elberegner.dk — Helping Danes pay less for electricity.