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 team/partners-in-crime

Chapter 05 · Act II · Growth

Partners in crime

2022 – 2026 · Vietnamese-German University

Work

never a solo project

One team, every semester, four years. Loyal, or very lazy about change.

The story

We met in the first weeks of 2022, sat in the same row by accident, and never split up. After that, every group project started the same way: someone asked “same team?” and nobody said no. Over four years we learned each other's habits: who writes the report at the last minute, who tests everything twice, who brings snacks to the late sessions. We argued about deadlines, fonts and variable names, and always made up before the presentation. The hardest moment was a semester when everyone was tired and the project was not. We split the work again, honestly this time, and finished. I learned more about teams from them than from any lecture.

If you're where I was

Keep the team that argues well, not the one that never argues. And write down who does what before anyone opens an editor.

Outcome

  • Four years of group projects, one team
  • Members lost: zero. Deadlines nearly lost: several
  • Seven people, five directions: security, business analysis, AI, development and project management

Skills

  • Collaboration
  • Disagreeing well

Small stories

  1. 50645bb“same team?” “same team.”
  2. b9b547aall seven of us in front of Notre-Dame, Paris

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