I’ve written software for over twenty years. The last four, I’ve spent building with AI almost every day.
Here’s the part I don’t usually lead with: I got laid off three times in five years. Same skills, same work ethic, same long hours. It didn’t matter. The third time, I stopped waiting for someone else to decide my work was safe, and I started building my own.
That’s really what this whole thing is about.
Somewhere in the middle of it, I was building a polling app with my sister, a physics professor, while a system I’d wired up ran the support loop for me. A ticket comes in, AI opens the issue, Claude writes the fix, it gets reviewed by Copilot, approved by ChatGPT, and deployed by GitHub Actions, so it ships. Heck, I even added browser automation to validate with post-production deployment, known as “smoke testing.”
And I watched it all happen from my office chair with an old episode of Monk playing in the background: multiple tickets submitted flew in and before the episode even ended, there were PRs, reviews, and deployments flying out, with testing reports showcasing the validated results.
That’s when it clicked: the barrier to building had collapsed. Not just for me. For anyone willing to sit down with these tools and a real problem.
Most people aren’t there yet, though. They could be. The noise is just exhausting. A new model every few weeks. A hundred tools, each one promising to change your life. The quiet fear that everyone else already figured it out. That’s overwhelm. And overwhelm is what keeps people stuck, more than any gap in what you know.
So that’s the job I picked. I help content creators, solopreneurs, and small businesses end AI overwhelm. Pick one real problem. Build the thing that solves it. Ignore almost everything else. I’ve done it for my own business, for the polling app a professor now runs with hundreds of students across multiple classes, for an email setup I run for a fraction of what I used to pay to rent the same thing. The move is the same every time, whatever you’re building.
I’m not selling a finished, polished guru version of this. I’m building in the open and showing the real process, including the parts that break, the milestones and successes when it works, and the receipts along the way.
What you get here: every week, one issue. I show you one real thing I use, the tech, a tool, or a way of working, and exactly how I use it. You can take it and run with it yourself. And when you’d rather not go it alone, there’s a way to do it together.
That’s the whole promise. One problem, one path, one week at a time.
If that’s useful to you, subscribe and stick around.
Thanks!
Ahad L. Amdani
