Start here

Who this is for

People who aren't sure AI is for them. People who started and got lost. People who feel like they missed something everyone else already knows.

None of that is true. Most people who look confident with these tools were confused six months ago. The ones who figured it out didn't have a special advantage. They just kept going past the awkward part.

I don't think the labels we've used to sort people will hold much longer. Technical, non-technical, builder, non-builder. The barrier is lower than it's ever been. This site exists because I believe that, and because I'm living proof of it.

Where you might be right now

Never tried it. Start with a conversation. Open Claude or ChatGPT and give it something real from your actual life. A document to summarize, an email to draft, a question you've been sitting on. Don't test it with a fake task. The gap between "interesting" and "useful" closes fast when the stakes are real.

Curious but overwhelmed. There are too many tools and too many people telling you their way is the right way. Ignore most of it. Pick one tool and use it until it feels boring. Then add another. Jumping between tools before you've gotten good at one is how you end up with thirty tabs and no skill.

Started building, got stuck. This is the most common place to stall. Something broke, or the output wasn't what you expected, or you hit a wall you didn't know how to climb. The answer is almost always: give the AI more context. Tell it what you tried, what happened, what you expected. Treat it like a collaborator who wasn't in the room and needs to be caught up.

The one thing that changes everything

Help the AI understand what you know and what you think you don't know. This sounds simple. It changes everything.

When you tell an AI your level, it calibrates. Like being assigned the right reading level in school. The output becomes something you can actually use instead of something you have to decode.

A bad prompt: "How do I build an app?"
A better prompt: "I want to build a simple booking form for a small business. I've never written code. Walk me through what I'd need and what tools make sense for someone starting from zero."

That's most of the skill. Specificity is the unlock.

If you're ready to build something

Take 30 minutes to learn what a terminal is and what an IDE is. You don't need to master either. Just understand the difference and decide how close to the tools you want to be. Then use a chat interface to talk through what you want to build before you build it. Reduce your plans to the simplest version that someone would actually want to try.

Don't build the car nobody drives. Build the thing people want to try, so you can learn from real reactions instead of imagined ones. Stability and security matter more than features. Ship the simple thing first.