I am not a developer, and that’s the point
I want to be straight with you from the first line. I have never been trained to write code. I don’t read it, I don’t write it, and a year ago the idea of “building a website” meant hiring someone and hoping they understood me.
This site — the one you’re reading — was built by me, with AI doing the parts I can’t. Not by a agency. Not by a friend who codes. By me, describing things in ordinary words and letting the tools turn those words into something real.
That’s the whole reason this notebook exists: to keep the honest record of how that actually works, so you don’t have to take my word for it.
The wall I kept hitting
When I first got the idea for a site, I did what most people do. I searched. Almost every guide I found opened with “install this, run that, clone the repo.” None of it meant anything to me. They were written for people who already spoke the language, not for the person standing outside the door.
So I did nothing for a while. The idea sat there.
What changed wasn’t me learning to code. It was the tools getting good enough that I could simply describe what I wanted and get a working first version back. The gap I couldn’t cross — write code — got bridged by something that reads English better than I read Python.
How I actually did it
Not magic. Just a loop I ran over and over:
- I described the page in plain words. “I want a home page that says I’m a non-technical founder, with a clear button to start, and a short list of what this site is for.” No code, just the picture in my head.
- The AI produced a first version. Rough, sometimes wrong, sometimes oddly close. Always a starting point, never the finish line.
- I read it like a human and pointed at problems in normal language. “This sentence is too technical — say it like I’d say it.” “The button should be bigger.” “Why is this part here at all?”
- We went back and forth until it felt right to me — the only judge that matters, because I’m the one who has to stand behind it.
That’s the job now. Not coding. Editing reality with words.
The tools I lean on
I’ll keep this honest and short. The center of it is a coding assistant that turns descriptions into working code — the thing that lets a non-coder ship a real site. Around it, I use a couple of writing and organizing tools so the words and the structure stay clear.
A note on trust: some links on this site are affiliate links. If I point you at a tool and you sign up through my link, I may earn a small commission at no extra cost to you. It never changes what I recommend. I only mention tools I actually use, and I’ll tell you the annoying parts too — because a tool that’s sold as perfect is the one you shouldn’t trust. (The full list of what’s sponsored lives on the affiliate disclosure page.)
If you want help picking the right tool for how you work, that’s exactly what the tool finder is for.
What still went wrong
This is the part the cheerful “AI builds it for you!” posts skip, and it’s the part you need.
- The AI writes a first draft, not a finished product. Left alone, it produces something that looks done and isn’t. My job is the judgment the machine doesn’t have.
- It can’t read my mind. “Make it nice” gets me nothing useful. “Make the headline say X, put the button below it, use plain language” gets me somewhere. Vague in, vague out.
- I still hit walls. There were days a change broke three other things and I had no idea why. I described the problem, we undid it, we tried a different path. Slow, but it moved.
- “No code” does not mean “no work.” The work moved from writing syntax to making clear decisions. That’s easier for me, but it is absolutely still work.
None of that means it doesn’t work. It means the promise “the AI does everything” is a lie someone is selling you. The real promise is better: you stay the boss, and the boring first draft is no longer your problem.
Why I’m telling you this
Because the version of me a year ago needed exactly one thing: proof that a person who can’t code could still make something real. Not a course, not a lecture — a record from someone actually doing it.
So this site is that record. The posts in this notebook are the real ones: what I built, what broke, what I’d do differently. If you want them as they happen, the email dispatch is the shortest path — I send what I learn as I learn it, and leaving takes one click.
Your move
If you’ve been sitting on an idea because “I don’t code,” start at the non-technical founder path. Four plain steps, no prerequisites, no install. Small beats ambitious here — pick one tiny thing and describe it.
That’s how this whole site began: one small, specific thing I wanted to exist.