Building & apps Claude

How I use AI coding tools as a non-programmer

You don't need a CS degree to build real tools anymore. Here's how I go from idea to working software.


I don’t have a tech background. No degree, no bootcamp. Everything I’ve built — video pipelines, automation scripts, a small website like this one — was built by describing what I want to an AI coding tool and checking what came back. Here is what I actually learned about making that work.

Describe the outcome, not the code

The biggest beginner mistake is trying to sound technical. You don’t need to. “When a new order comes in, I want a message in my Telegram with the order details” is a perfect instruction. The AI translates it into code; that’s its job, not yours.

Always ask for a way to verify

This is the one habit that separates people who ship from people who give up. Every time the AI builds something, ask: “how do I check this actually works?” Then do that check. Run the thing. Click the button. Send the test order. Code that hasn’t been run is code that doesn’t work yet — that rule has no exceptions.

Errors are conversation, not failure

When something breaks, copy the error message and paste it back. That’s it. Error messages look terrifying and are actually the most useful text in the whole process — they tell the AI exactly what to fix. I’ve fixed hundreds of problems knowing nothing more than copy and paste.

Keep every project small

One tool, one job. A script that renames your files. A page that shows your orders. Small projects finish, and finished projects teach you more than ambitious abandoned ones. When a small tool proves useful, grow it.

Save your working versions

Ask the AI to set up “version control” (git) on day one. It’s a save-game system for projects: every time something works, you snapshot it. When a later change breaks things — and it will — you roll back instead of despairing.

What I’d tell past me

The gap between “I have an idea” and “I have a working tool” used to be years of study. It’s now an afternoon of clear description and honest checking. The skill you’re actually learning isn’t coding — it’s saying precisely what you want and refusing to accept “looks done” over “proven done.”

Free, occasionally

New guides, straight to your inbox

When I figure something out worth writing up, you get it. No spam, unsubscribe anytime.

← Back to all guides