Journey

Five acts, eleven chapters, one line. Open any point.

The journey, mapped

  1. 01 · September 2022Hello, worldA new campus, a new password, and a program that finally said hello back.
  2. 02 · 2022 – 2023First year, first shockLess “listen and copy”, more “here is a problem, good luck”.
  3. 03 · 2023First thing I builtThe first project that had to work somewhere other than my laptop.
  4. 04 · 2023 – 2024Finding my peopleThe people who turned campus from a timetable into somewhere I wanted to be.
  5. 05 · 2022 – 2026Partners in crimeOne team, every semester, four years. Loyal, or very lazy about change.
  6. 06 · 2022 – nowOne great routineTwice a week I close the laptop and go get hit by a volleyball. Voluntarily.
  7. 07 · WS 2024/25Studying in GermanyA semester in Germany: new university, new language, punctual trains (mostly).
  8. 08 · 2024 – 2025Travelling EuropeFour countries, a lot of trains, and a student budget held together by bread.
  9. 09 · 2025Choosing project managementI liked writing code. I liked it more when the whole team's code shipped on time.
  10. 10 · 2025 – nowLearning to be a project managerNot a PM yet. Practising on everything, including the site you're reading.
  11. 11 · 2026Still being writtenGraduating on 20 November 2026. The next chapter is still a draft.

cat README.md

Chapter 10 · Act V · Now

Learning to be a project manager

2025 – now · Real projects, including this website

Work

learned more in 3 months

Not a PM yet. Practising on everything, including the site you're reading.

The story

I'm not a project manager yet. I'm practising on purpose, and this website is one of the projects: a written brief, research, sketches in Figma, a build plan in milestones, a definition of done, and a review before every release. Most of the code was written by a team of AI agents. My job was the PM part: deciding what to build, writing briefs clear enough to follow, saying no to good ideas that didn't fit, and checking the work before it shipped. I learned that a vague task comes back vague, that “almost done” is a status, not a fact, and that the most useful thing to bring to a meeting is the question nobody has asked yet.

If you're where I was

Practise on a real project with a real deadline, even a small one. Write the plan down, then notice where reality disagrees: that gap is the lesson.

Outcome

  • Ran this site from brief to release in milestones, every release reviewed
  • Kept a decision log for every change of direction (D1 to D56 so far)

Skills

  • Scoping and milestones
  • Writing clear briefs

Small stories

  1. rewrote a vague brief, got the right thing back

Missions

ben.test.ts · explore to pass them all · the gift waits at the end

opening

highlights

origin

growth

roaming

next: pick who you are — say who you are reading as → jump

0 of 10 missions done

gift: locked