1. Guide
Explains how you could build a project. It does not mean I built it.
I have not published a project here yet
When I finish a project I can properly explain, this is where it will go. Below is what a project needs before it lands here.
FOUR KINDS
Four different things get called a project here
2. Example
Sample code, a circuit or a design used to show one idea.
3. Work log
Dated attempts, mistakes and the changes that followed.
4. My own project
Whose idea it was, what I built, the tests, the sources, and permission to publish.
MY CHECKLIST
What I check before a project goes on this page
| Topic | What I will write | What I will not write |
|---|---|---|
| Problem | What was needed and who would use it, in my own words | Someone else’s private situation, or personal details |
| Solution | Diagram, algorithm, materials and version | A ready-made project presented as something I built |
| Contribution | Who did which part | A teammate’s name or photo without their permission |
| Testing | What I expected, what happened, where it failed | Only the attempt that worked |
| Sources | The code, images, data and licences I used | Copied material with no clear origin |
| Safety | Electricity, tools, data and adult support | Details that would tempt someone to repeat something unsafe |
| Permission | Consent for photos and personal information | Document numbers, location, private contact details |
PROJECT FILE
Getting a project ready to explain
Something working once does not mean it is finished. Whoever reads the page should understand what I did, be able to repeat the same test, and find the sources I used. Before a project goes up here I will:
- write down the date and the version number
- keep my first problem statement next to the final one
- list the materials, software, data and licences I used
- show at least one failed attempt and what I changed afterwards
- say so if a ready-made module, AI help or an adult was involved
- remove personal details and location from photos and screenshots
- note what a second version would try and what it would test
GUIDES ON THIS SITE
Three project guides on this site
micro:bit step counter
On sensor data, thresholds, false counts and privacy.
Open the guide →Reaction-time game
On timing, latency, repetition and fair comparison.
Open the guide →Accessible sport dashboard
On showing data with keyboard access and signals beyond colour.
Open the guide →HOW IT GETS ADDED
When does a project land here?
A project goes up when I have finished it and can explain it to someone else. Not just the result: the problem, how I built it, where I got stuck, the sources I used, the safety side, and the part that is genuinely mine.
I will write up the attempts that did not work as well. And if I ever take a project down or change it, I will not do it quietly — I will say why.