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.

git checkout project/works-on-my-machine

Chapter 03 · Act II · Growth

First thing I built

2023 · A team project at VGU

Work

ugly, but it worked

The first project that had to work somewhere other than my laptop.

The story

The brief fit on one slide. The project did not. We had a few weeks, one shared repository and several different ideas of what “done” means. I took the parts nobody else wanted, broke the main branch twice, and learned what a merge conflict feels like at 1 a.m. (cold). The night before the demo it worked on my machine and nowhere else; we fixed it over breakfast. On demo day it ran, mostly, and when the lecturer clicked the one button we had never tested, that ran too. It was ugly and it was slow, but it was ours, and it taught me that building software is mostly people agreeing on things.

If you're where I was

Start before you feel ready, and put it in git from the first hour. Ugly and finished beats beautiful and still in your head.

Outcome

  • A working demo, shipped with my team on deadline
  • Learned git the honest way: by breaking main

Skills

  • Git
  • Shipping under a deadline

Small stories

  1. b06d01finitial commit
  2. 9315499demo day: it ran
  3. 3989831the untested button worked anyway

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