David caught me right after the daily standup.
"Kai, I want you to lead the microservices migration in Q3."
My first thought: Nice. Promotion material.
My second thought, about 0.3 seconds later: Wait. Am I qualified for this?
The Comfort Zone Is Really Comfortable
I'm 35. I've been writing code professionally for over a decade. I can debug a production outage at 7 AM before my coffee kicks in, review PRs in my sleep, and explain distributed systems to junior devs without sounding like I'm reading from a textbook.
But lead architecture? For the entire backend? That's different.
That's making decisions other people will have to live with for years. That's choosing between gRPC and message queues, between monorepo and polyrepo, between "let's be clever" and "let's be boring." It's not just code anymore — it's responsibility.
I told David I'd think about it and reply by end of week.
Dead Cells Taught Me Something
That evening, I hopped on Discord with my friend Tùng. We've been gaming together since the CS 1.6 days in Vietnamese internet cafes — 20 years now. He just bought the Dead Cells DLC and wanted to try co-op.
Tùng was terrible. Kept rolling into spike pits. Died four times on the same Clock Tower section. At one point I was literally carrying him through the level while he complained about his new controller.
But here's the thing: every time he died, he respawned and tried a different approach. Different route. Different weapon combo. By the end of the session, we'd unlocked two new bosses and several blueprints.
Dead Cells doesn't let you stay in one biome. You either push forward into harder areas, or you die and restart from the beginning. There is no "comfortable middle."
I realized at 10 PM, lying on my couch with 147 unplayed Steam games staring at me: I've been farming the same biome in my career for too long.
The Decision Framework
I'm not going to decide based on fear. Here's my actual framework:
What I gain if I say yes:
- Architecture design experience I can't get any other way
- A seat at the table for major technical decisions
- Something to point at when someone asks "what did you build in 2026?"
What I lose if I say yes:
- Free evenings (temporarily)
- The comfort of being "just" a senior engineer
- The ability to blame someone else when things go wrong
What happens if I say no:
- Same role, same comfort, same ceiling
- Someone else leads the migration
- I spend Q3 wondering "what if?"
The math is pretty clear.
It's Not Really About Architecture
When I strip away the fear and the imposter syndrome, this isn't about whether I can design microservices. I've been doing pieces of that for years. It's about whether I'm willing to step into a bigger room.
At 25, I thought 35-year-old me would have all the answers. Turns out 35-year-old me just has better questions — and a better understanding of what's actually scary.
What's scary isn't the technical challenge. It's the visibility. The accountability. The fact that if this migration fails, it's on me.
But Dead Cells taught me: you only unlock new areas when you stop replaying the same biome.
I'm building tools to automate the boring parts of my workflow so I can focus on the big decisions. Here's my Telegram Bot Starter Kit — handles notifications, cron jobs, and alerts while you're busy leveling up your career.
What's your career biome right now — farming the same level, or pushing into uncharted territory?
Top comments (0)