Skip to main content

He Can Debug Any System Except His Son

Updated 6 min readMarkdown

A 40-year-old software engineer went online recently to ask for help.

"I've mastered code," he wrote. "But I can't handle my 8th-grade son."

His son is good at math. He is also hooked on Fortnite. When he wins, he laughs out loud. When he loses, he can sink into a gloom that lasts for days.

The father doesn't want to scold him. But he doesn't know what else to do.

"Is coding a good path? I don't know. But it's the skill our family lives on. I don't really want him to walk the same road. Was it hard along the way? Honestly, what I care about more is how much hair I've lost."

"Playing games — if he's good at it, I think that's fine. It's just that on this road, he's gone a bit too far, but not deep."

That last line stopped me cold.

  1. Code throws errors. Kids don't.

A programmer's greatest skill is debugging. Something breaks, you read the log, reproduce it, fix it, run the regression tests. Every problem has a procedure.

But a child comes with no logs, no error messages, no stack trace. He's gloomy — is it because he lost a match, or because something happened at school, or because of some teenage feeling he can't even name?

The father's helplessness comes from exactly this: the tool he is best at fails on the person he cares about most.

Many parents of our generation grew up believing every problem has a solution, effort always pays off, any system can be optimized. Then a child arrives, and you discover some systems have no documentation, no API, and no debugger.

  1. What makes him gloomy may not be the game itself.

The most interesting thing about the replies he got is that nobody's first instinct was to blame the kid. One commenter put it plainly: no wonder he swings between happy and gloomy — the matchmaking keeps handing him a win, then a loss. It's hard not to be gloomy.

Modern competitive games use skill-based matchmaking with one core goal: pin your win rate near 50%. The better you get, the stronger your opponents get. Win a few in a row, and the system serves you tougher lobbies. That's not a bug. That's the design.

A 13-year-old rides that 50% roller coaster every day: win, dopamine; lose, crash. His mood swings aren't fragility. The product is working as designed.

The father sees "my son is emotionally unstable." The system sees "retention targets met."

That is the part worth thinking about. We imagine our kid is fighting the game. In reality he's fighting an addiction machine tuned by hundreds of engineers. And the father is fighting it alone.

  1. What the father really fears is "too far, but not deep."

The line that hit me hardest in the whole post is this: "he's gone a bit too far on this road, but not deep."

The father didn't say "games are trash." He didn't say "gaming gets you nowhere." He said: you've poured so much time into this, and you have nothing portable to show for it.

That's the real anxiety of middle-aged parents. Not moral anxiety — compounding anxiety.

Programmers understand compounding better than anyone. A function you write today still works next year. A mistake you make this year becomes experience next year. Time invested accumulates.

But a rank, a skin, a win rate — the season ends and it all resets. The game will still be there next year. But what will he carry away from it?

The father isn't against fun. He's worried about where the time goes.

  1. The best advice in the replies was never "take it away."

A few replies are worth copying down for every parent:

First: "Don't build a vertical relationship — a hierarchy. Build a horizontal one." Once father and son become boss and subordinate, communication becomes orders and compliance. A kid doesn't tell his boss the truth. He just performs.

Second: "If his whole friend group plays it, the game has become social." Confiscating the phone doesn't just remove a game — it expels him from his social circle. Without a replacement social life, quitting only brings isolation.

Third: "Give him something more fun to replace it." Not "you're not allowed to play," but "is there something better?" One commenter joked: give him a GitHub account, a five-dollar VPS and a domain name — more fun than the game, trust me, it runs in the family. It sounds like a joke, but the logic is right: you can't ban an interest away. You can only outcompete it with a more attractive one.

Fourth: "You may have a template of a good kid in your head. Don't blame him for not matching it. Guide him from where he already is."

And one more, quietly devastating: "Relax — it's the 'other people's kids' effect." The 13-year-old who runs his own servers? There are only a handful of them on the entire internet. Comparing your kid's ordinary days to someone else's highlight reel is a game you are guaranteed to lose.

  1. He doesn't want his son to walk his road. But that road feeds the family.

There's a contradiction at the heart of the father's post. He doesn't know if coding is a good path — and yet it's the skill the family lives on. He doesn't want his son to walk the same road — and jokes that the road cost him his hairline.

That's a tension many parents around 40 share: we survived on a road we're not sure is worth walking again. We want our kids to skip the suffering we went through — and we're afraid they'll grow up without ever learning to endure anything.

But maybe the question was never "which road." Maybe it's "how deep."

Code, games, football, piano, painting — dabbling isn't the problem. The problem is pouring huge amounts of time into one place and staying forever in the shallows. Depth is time's best friend.

So the question the father is really asking may not be "how do I make him quit the game." It may be: "how do I help him find something worth going deep on?"

There is no standard answer to that.

But at least the answer isn't in confiscating the phone.

Three questions for you:

  1. If your kid is destined to be obsessed with something, what would you want it to be?
  2. What were you obsessed with as a kid — and what happened to it? Did you outgrow it, or did someone take it away?
  3. What does a "horizontal relationship" between parent and child actually look like in practice?

Tell me in the comments.

1 view

About the author

  • I'm Wayfinder, a project manager. I build small internal tools with AI and write about what it gets wrong — and right. My weekly newsletter is Output Mode on Substack.

No comments yet. Be the first to comment.