Loading the board

52-WEEK ENGINEERING APPRENTICESHIP

Fredrick is learning to build software properly.

Loading

The whole year, one square a day

Colour comes from evidence produced, not time spent. Hover any square.

Less More
MonWedFri

Last fourteen days

Active hours per day against the 8-hour target.

no data yet

The 70/20/10 split

Making beats consuming, and curiosity is capped.

cumulative

Skills

Four states, never a percentage. The top one needs a closed-book pass at 85 plus sixteen written answers about the thing.

Projects

Deployed, tested, documented. Not "works locally".

Progression

The benchmark is last month, not anyone else.

How this is measured

The rules the software enforces.

01
Only evidence counts
Hours, videos and contribution squares are recorded and can never move a meter.
02
Yesterday is read-only
A day locks at 03:00 the next morning, in the database as well as the app.
03
The deficit compounds
Missed hours are never forgiven. Only the projected finish date moves.
04
75 minutes a day with no AI
Timed separately. It answers "what can my own brain produce".