What to Build

You've got your editor, Git, and Hackatime set up. Time to actually build something. There's no wrong answer here, pick a path based on how confident you feel.

Follow a guide

If you want a clear path from zero to a finished project, start with one of ours. Each guide walks you through a real build step by step, so you end up with something you can actually ship.

Build anything you want

You don't need permission from us to build something. If an idea has been bouncing around your head (a game, a tool, a website, a bot, a weird experiment), that's a perfectly valid project. Pick something small enough that you can see the end of it, start it, and iterate as you go.

A few rules of thumb:

• Smaller than you think. Your first pass should fit in a weekend. Bigger ideas can come later once you know what finishing looks like.
• Solve something real. Even if it's just for yourself. A project you actually use stays fun to work on longer than a project you don't.
• One feature at a time. Get the boring core working first, then stack features on top. Don't try to architect the whole thing upfront.

Look up what other people are making

YouTube is full of build walkthroughs you can learn from and remix into your own project. A few channels worth a subscribe:

• Fireship does fast-paced overviews of modern web tools and "build X in 100 seconds" videos. Great for finding tech you want to try.
• The Coding Train walks through creative coding projects (generative art, games, simulations) with a very beginner-friendly vibe.
• Ben Awad streams full-stack builds end to end, which is a nice way to see how real apps are structured.
• Web Dev Simplified breaks concepts down clearly and often builds small projects you can follow along with.

Also worth a search:

• "your language/framework project ideas for beginners"
• "build a thing you use every day from scratch"
• "skill you want to learn tutorial"