Blog / Build with AI /
A weekend project plan for absolute beginners
Most first projects die in the planning stage, or on Saturday afternoon when the AI produces something confusing and you aren’t sure what to ask next. A good plan doesn’t need to be clever. It needs to be small enough to finish and specific enough to follow.
Here’s a plan for a weekend, written for absolute beginners. The goal: by Sunday evening you have one small, working thing that you made, understand and can show someone.
Pick the right project
Choose something that meets all four tests:
- You’d use it yourself. Motivation matters more than originality.
- It fits on one page. No accounts, no payments, no database.
- You can describe it in one sentence. “A page that converts miles to kilometres” passes. “A platform for fitness” doesn’t.
- You can tell if it works. A calculator is easy to check. “A tool that makes my writing better” is not.
Good starter ideas: a tip splitter, a countdown to an event, a unit converter, a habit checklist, a simple quiz, a packing list. If you need inspiration, building a habit tracker with AI and building a word counter and readability checker are both small enough for a weekend.
Friday evening (30 minutes): decide and prepare
- Write the one-sentence description.
- List the three things it must do. Only three.
- List what it will not do. This one is important: “no login, no saving online, no fancy design”.
- Install a decent code editor, or decide to use an AI chat that can show you a preview. Either is fine.
- Create a folder for the project.
Then stop. Resting is part of the plan.
Saturday morning: get a first version running
Describe your project to an AI tool using your three musts, your won’ts and your constraints:
I’m a beginner. I want to build a single HTML page, with plain HTML, CSS and JavaScript in one file, that does the following: [your three things]. It should not [your won’ts]. Explain what each part of the code does in simple language, and tell me exactly how to run it.
Save the code as index.html, double-click it, and see what happens. Whatever it looks like, that’s progress. A rough thing that runs beats a perfect plan that doesn’t.
If you want to see how to ask in a way that prevents guesswork, read making AI ask you questions before it builds.
Saturday afternoon: understand it, then change one thing
This is where beginners learn the most, and where many skip ahead.
- Ask the AI to explain the code section by section.
- Pick one tiny change and make it yourself, like altering a colour or a label.
- Break something on purpose, then fix it. Delete a bracket, see the error, restore it.
If you can change a colour and fix a typo, you’re no longer just copying. You’re editing.
Saturday evening: list what’s wrong
Use the tool as a real user for ten minutes. Write down everything that annoys you, then sort the list:
- Must fix: broken things.
- Should fix: confusing things.
- Nice to have: everything else, which you will probably ignore.
Sunday morning: fix the must-fixes, one at a time
For each item, give the AI a precise description:
When I type a negative number, the result shows NaN. It should show the message “Please enter a positive number”. Change only that behaviour and show me the changed lines.
One bug per message. Test after each change. If something gets worse, go back to your last working copy. Save a copy before every big change, even if that just means duplicating the file and renaming it index-v2.html. Git basics for non-developers is the next level when you’re ready.
Sunday afternoon: test with another person
Give it to a friend or family member and say nothing. Watch what they do. Where they hesitate is where your tool needs work. It’s humbling and extremely useful.
Then fix one or two things from that, not ten.
Sunday evening: finish
Finishing has a few parts, and they’re easy to skip:
- Give it a proper title and a sentence explaining what it does.
- Test it on your phone.
- Put it somewhere you can reach it: a free static host, or simply keep it on your computer.
- Write three lines of notes: what it does, what you learned, what you’d add next.
Then stop. Resist the urge to add one more feature.
What if you get stuck?
You will, at some point. The usual causes are small. The page is blank because of a typo or a missing bracket. A button does nothing because its name in the code doesn’t match its name in the page. Open the browser’s developer console (right-click, Inspect, then Console) and read the red message. Paste that exact message into your AI chat along with the relevant code and ask what it means in plain English. Error messages look hostile, but they usually point to the line that needs attention.
If three attempts at the same fix have failed, stop and go back to your last working copy. Then try a smaller version of the change. Progress on a weekend project is mostly about not losing what already works.
Rules that save weekends
- Smaller than you think. Halve the scope, then halve it again.
- One change at a time.
- Don’t paste secrets such as API keys or passwords into AI chats.
- If you’re stuck for more than 30 minutes, simplify. Remove the part that’s causing trouble.
- Done beats perfect. A finished ugly tool teaches you more than an unfinished beautiful one. See turning a weekend project into something people use for what comes next.
Key takeaways
- Pick a one-page, one-sentence project you’d use yourself.
- Write down what it won’t do.
- Get something running early and improve in small steps.
- Test with a real person.
- Finish, note what you learned, and stop.
Related reading
- Building a unit converter with AI
- Building a simple API for your own data with AI
- Git basics for non-developers before you build with AI
What will your project be?