LESSON 06 / 15 MINUTES
You started with an idea and a blank folder. Now you have a working first version, some test results, and a few decisions that are yours. Let’s make sure you can carry that process into the next project.
1. Give someone the two-minute tour
Show a classmate your planner, or talk through it yourself. Add a task, change the time filter, and mark something complete. Explain who you made it for and why you changed one part of the first version.
Then answer this without asking Codex to write your response: How does your planner choose the next task? If you’re not sure, return to the explanation in Lesson 4, check the behavior, and try again in your own words.
2. Keep a small record of the work
If your instructor gave you submission directions, follow those. Otherwise, use this as a completion checklist for yourself:
- The project: your final index.html file, plus any other files if you expanded beyond the shared activity.
- Before + after: the first-version screenshot from Lesson 4 and the improved-version screenshot from Lesson 5.
- Your direction: the initial brief and one follow-up prompt that improved the result.
- Your checks: at least three test results, including what you actually tried and what happened.
- Your explanation: a short reflection in your own words.
WHICH TWO SCREENSHOTS?
Before: Use the screenshot of your first planner version from Lesson 4. If you missed it, open the index-before-changes.html backup from Lesson 5 and capture that earlier version. Add a one-sentence caption saying what was confusing, missing, or broken.
After: Use the screenshot you took after your improvement in Lesson 5. Show the same part of the planner, ideally at the same window size and with the same sample task. Add a one-sentence caption saying what changed and what happened when you tested it.
REFLECTION / ABOUT 150–250 WORDS
What did you want to make, and for whom? What did Codex do well? What did you have to correct or clarify? Describe one test you ran yourself: what did you click or enter, what did you expect, and what happened? Then explain one rule your app uses, such as how it picks the recommended task. What would you change next?
Be specific. “AI helped a lot” doesn’t tell us much. “The filter included completed tasks, so I asked Codex to exclude them and retested with a 20-minute task” tells us what you learned.
A clear account of your process matters more than pretending the first attempt was perfect. Acknowledge Codex’s role and any other sources, code, or assets you used. Your instructor’s disclosure requirements take priority.
3. Know what you’re sharing
Sending the project file is different from publishing a website. For this module, a local file and screenshots are enough unless your instructor says otherwise. If you later publish, remove personal information, check any asset licenses, and follow your course’s hosting instructions. Don’t publish account keys or private data.
Before you call it done
Codex says every test passed. Do you still need to open the app?
Yes. Ask which tests it ran, but also try the important interactions yourself. Automated checks and a person using the app can catch different problems.
You want a major redesign. What should you do first?
Save a working copy or commit your changes. Then describe the redesign and the behavior that should stay the same. Test again afterward.
You’re stuck. What belongs in the next prompt?
The steps you took, the actual result, the expected result, and the relevant error or screenshot. Keep the request focused enough that you can verify the answer.
BEFORE YOU MOVE ON
You can describe, build, try, and revise with Codex. You also know when to slow down and check. That’s the skill you’ll take into the next project. Now, go make something you actually want to use.