Dead Cells, Career Crossroads, and Why I Still Play Games at 35
Tonight I did something I've been doing for 20 years: logged into Discord, joined a voice channel, and played games with my best friend Tùng until almost midnight.
We were running Dead Cells co-op — specifically the Return to Castlevania DLC. Tùng kept dying in the Clock Tower. Like, embarrassingly dying. Rolling into spike pits. Forgetting to parry. The kind of deaths that make you question whether your friend even has thumbs.
I was cackling. He was swearing in Vietnamese. It was exactly like 2006, when we'd sit in a smoky internet café playing CS 1.6 until the owner kicked us out at 2 AM. Same energy. Same friendship. Just different games and slightly worse reflexes.
But here's the thing: earlier today, my boss David asked me to lead our microservices architecture migration in Q3. It's the biggest career opportunity I've had in five years. I should be spending every evening studying system design patterns, reading about event-driven architectures, maybe even prototyping some POC on the weekend.
Instead I spent three hours dying repeatedly to a pixel-art clock tower with my friend.
And honestly? I think that made me a better engineer tomorrow than any architecture book would have tonight.
There's something about the flow state of gaming that resets my brain in a way nothing else does. Coding requires flow. Architecture design requires flow. But both of those are productive flow — there's a deliverable, a deadline, a PR at the end. Gaming is purposeless flow. The only thing you're optimizing for is not face-planting into a spike pit.
After a day of debugging production payment failures (spoiler: it wasn't my retry logic, it was the upstream provider silently changing rate limits — classic), my brain was fried. The circuit breaker pattern I implemented this morning was solid, but the decision fatigue from the David conversation was eating at me.
Dead Cells didn't solve my career dilemma. But it gave me three hours of not thinking about it — and sometimes that's exactly what you need to see the answer more clearly.
I'm 35 now. When I was 25, I thought 35-year-old me would have everything figured out. He doesn't. He still plays video games with his best friend, still debates whether to step up or stay comfortable, still writes questionable code at 2 AM (note to self: stop doing that).
But he also knows something 25-year-old me didn't: the space between decisions — the gaming sessions, the balcony coffees, the Discord calls with your sister in Australia — those aren't distractions from the work. They're the scaffolding that makes the work possible.
Tùng logged off at 10:30. We'll play again this weekend. And sometime before then, I'll give David my answer about Q3.
I think I already know what I'm going to say.
Now if you'll excuse me, I just added "Mossheart" to my Steam wishlist. It's a pixel-art roguelike. I'll probably buy it on sale and never play it. Some things don't change.
🛠️ If your code spends more time fighting APIs than solving problems, check out my *Python Revenue Engine** — 10 production-ready automation scripts with built-in circuit breakers, rate limiters, and proxy rotation. Drop in, ship fast.*
Top comments (0)