I kept shipping — without making code my identity.
I care that it ships. I never needed “developer” as my name. That turned out to be a kind of craft anyway.
I care that it ships. I never needed “developer” as my name.
For years the path looked like this: whatever got the business live. Builders. Design tools. CMS. Commerce platforms. Then AI workspaces. From the outside it can look scattered. From the inside it was one job — make something real enough to put in front of people.
Surface
Sites, stores, landing pages
Shape
Design tools when it had to look right
Memory
CMS and databases when content grew
Glue
Domains, DNS, hosting, funnels
Identity-wise I stayed closer to builder and operator than to syntax specialist. If there’s a skill here, it isn’t genius. It’s staying with the broken thing long enough that shipping became more familiar than quitting.
What I actually practiced
Not one deep specialization. A lot of adjacent ones. Enough DNS to unstick a domain. Enough hosting to get a site up. Enough funnel and CRO instinct from product work to care whether anyone arrives. Enough commerce platforms to know a store is never “just a theme.”
I’m not sure how common that profile is. Founders who don’t code, but aren’t fully non-tech either. People who learned the digital surface by fire. I don’t need a perfect label for it. I know what it feels like when something won’t go live — and I know I usually stay.
Copy, paste, glue. Chat in one window, files in another. Still shipping — just slower, with more friction between idea and artifact.
Same builder itch. The partner sits in the project. Less glue. Files change where they live. The habit finally has a workspace that matches it.
AI harnesses didn’t invent this way of working. They finally matched it. That’s why I teach the way I do — first principles while building live, not a syllabus that assumes you already love syntax.
If you want a week inside the AI IDE craft — Cursor now, workflow that travels later — start with the 7-day Cursor workshop.