How I work
Roughly three steps
- 1
Data and architecture first
Where the data comes from, who touches it, where it ends up — and how the pieces fit together. Get that right and the app behaves like a living system. Get it wrong and it behaves like my first WoW server.
- 2
Let Claude type
The syntax used to eat my twelve-hour days. Now Claude writes it, in whatever language the project needs, and I get to do the fun part.
- 3
Check its homework
Claude is fast and very sure of itself. Somebody has to actually read what it wrote. That somebody is me.
House rules
A few house rules
Data and architecture first, code second
If I don’t know where the data goes and how the pieces fit together, I don’t write the code. Yet.
No duct tape
Fix the problem where it lives, not where it happened to show up.
Language? Whatever.
The logic is the same in every language. Only the syntax changes, and the AI handles that bit.
Trust, then verify
Mostly verify. The AI writes fast, I read slowly. It works out.
Hands off my server
An AI restarted my dev server once. Once.
Twenty drafts, one winner
Old habit from the pre-AI days. The difference: now the twenty drafts take minutes.
FAQ
Questions nobody asked
Depends who’s asking. The typing was never the hard part — knowing what to build was. That part didn’t go anywhere.
Mostly JavaScript and TypeScript — Vue, Nuxt, React, Node, NestJS — plus Laravel, a bit of Python, C++ and C#. I started listing the rest and got tired.
I started at twelve. Then I took a ten-to-fifteen-year detour through football, furniture and bartending. Not late. Scenic.
Yes. Somebody has to. Claude doesn’t mind.
Nope. I’m happy where I am. This site is just here to say hi.