Student Spotlight: How 15-Year-Old Amara Built a Result Checker for Her School

Amara is fifteen, in SS1, and until January she had never written a line of JavaScript. Her project is now used by roughly 300 students every term. We asked her to walk us through the whole build, because her process is a template any teen can copy.

The problem was boring — which is why it worked

Result slips were printed and often mixed up, so students queued at the staff room. Amara did not start with a technology; she started with a queue she stood in twice a term. Good first projects almost always come from an annoyance you personally experience.

Ten weeks, four milestones

1. Weeks 1–2: a static page with a form and a fake result, just to get the layout right.

2. Weeks 3–5: real data from a spreadsheet her class teacher already maintained.

3. Weeks 6–8: access codes so students could only see their own results.

4. Weeks 9–10: testing with twelve classmates, then a demo to two teachers.

What she would tell another beginner

“Show it to people before it is ready. The first version of my form asked for a surname, and three of my friends typed their first name instead. I would never have found that alone.” That single test changed the design more than any tutorial did.

If you want to build something like this with weekly guidance, look at our cohort programs or read the 30-day beginner roadmap she followed.