From Tehran to Munich: An Initial Commit

Every developer knows the feeling of that first commit. The blank repository, the cursor blinking, the weight of possibility. My life has felt like a series of initial commits — each one in a new city, a new language, a new version of myself.

# v1.0.0 — The Bootstrap

Arriving in Kuala Lumpur from Tehran was my first major deployment to production. Everything was unfamiliar. The language, the food, the weather, the way people interacted. I was running in debug mode constantly, trying to parse every social interaction, every cultural nuance.

But here's what I learned: humans are remarkably adaptable systems. Given enough exposure and a willingness to fail publicly, you can rewrite your own firmware.

# The Bug Fixes

The early years were full of what I now think of as bug fixes. Assumptions that needed correcting. Mental models that needed updating. The biggest bug fix was shifting from a student mindset to a professional one — understanding that in the real world, nobody gives you a rubric.

# Scaling Up

Each subsequent move — to Prague, then to Munich — came with its own migration challenges. But each one was easier than the last. Not because the challenges were smaller, but because I'd built better tooling for handling change.

# The Lesson

If I could distill everything into a single commit message, it would be: "feat: embrace uncertainty as a feature, not a bug."