Why I’m Writing This

Part 7 of 11 — Vibe Coding for Non-Developers


I don’t really post.

I have a LinkedIn because I know my network is well ahead of me on this. They’ve been building with AI for longer, made mistakes I haven’t made yet, and figured things out I’m still figuring out. I’m there to learn from them, not to perform for them. I scroll more than I share. I’ve watched other people document their journeys — the builds, the pivots, the things they learned — and thought: good for them. I could never.

That changed when I started this project.

Somewhere in the middle of it — somewhere between the FK documentation and the commented-out code and the password I couldn’t remember — I realised I’d been carrying this problem for so long that I’d stopped asking whether it could be solved differently. That moment sat with me.

I’m not an engineer. I have a regular job. This happened in a weekend and a few evenings. I made bad decisions, hit walls, texted people who knew more than me, and kept going. The app isn’t finished. The blog isn’t polished. I wrote these posts and rewrote them and rewrote them again because getting the voice right turned out to be as hard as getting the code right.

But it’s real, and it works, and it’s solving the problem I built it for.


← Part 6: Your Network Is a Vibe Coding Tool. Most People Forget to Use It. · Start from the beginning →