What a milestone is
A milestone is a small, finished step: a group of related features that is built, checked and recorded before the next one starts. “Finished” is the key word; a half-built feature does not count.
Working in milestones keeps every change small enough to understand. When something breaks, the cause is almost always in the step just taken, which makes bugs cheap to find.
How to plan and finish a milestone
- Choose a small scope: one capability, or a few closely related ones.
- Decide what “done” means before starting: what must work, and how it will be checked.
- Build it, then test it, including the earlier tests, so nothing that worked before has broken.
- Look at the result on real screens, not only through tests.
- Update the documentation in the same step, so it never describes an older version.
- Record what changed and what is still true, in a changelog and a status file, including what was not tested.
This site
The site grew through four numbered milestones (foundation, design refinement, personal content and CV, contact workflow). A hardening pass then ran in five checkpoints: fix critical bugs, add broader tests, centralise content, and prepare for launch. After each checkpoint the changelog and a project status file were updated, and the earlier test suites were re-run to catch regressions. One of those runs caught a bug I had just introduced, a helper function used before it was defined.
Later work kept the same rhythm: a security review, then a redesign, then a check for the content file, then a page for every project and note. Each change ended with every test suite run again and every affected document updated before the next began. The tests grew with the site, to fourteen test files and more than two hundred and seventy checks.
GPA Tracker
GPA Tracker was built across six milestones. The write-ups record a pattern of adding one capability at a time: safer error handling, grades derived from saved marks, edit-in-place, backups and export, the planner, and a stronger test suite. Because each step was checked before the next, bugs such as the freezing backup were found while that feature was fresh.
Letting the computer run the checks
Running every test by hand depends on remembering to. A GitHub workflow now runs all of them on every push, checks that generated files are up to date, and marks each change with a pass or a fail. It does not stop publishing; it warns early.
Saying what was not tested
Each report on this site lists what its tests could not cover: other browsers, real phones, screen readers, and real message delivery. Writing that list stopped me from claiming more than the evidence supports.
Planning for later features
Moving content into one data file means a new project is one added entry, not another block of copied markup. The same data shape leaves room for a backend later without building one now.