Skip to main content
SubZeroDev

Professional uncertainty since 2026.

Well… Why not?


What the Fuck Are You Doing, You Maniac?

· 5 min read

Back in college, somewhere in the late 1990s, I knew a programmer named Chris.

Chris was brilliant.

Not "good at programming."

Not "smart guy."

Brilliant.

The kind of programmer you remember twenty-five years later because your brain quietly filed him under:

This motherfucker is operating under different rules.

This was back when the web was still held together with hope, table layouts, browser-specific nonsense, and Netscape doing whatever the fuck Netscape felt like doing that particular afternoon.

Normal people looked at web browsers and thought:

"This thing is kind of shitty."

Chris looked at web browsers and apparently thought:

"I should write one."

In C++.

A whole fucking browser.

I remember looking at him with some version of the expression people reserve for a man calmly assembling a helicopter in his kitchen.

What the fuck are you doing?

You maniac.

There are browsers.

They already exist.

Yes, they are terrible.

That does not mean the obvious response is to sit down and create another one from fucking scratch.

And yet there he was.

Writing a browser.

Because apparently the existence of a difficult problem is, to certain programmers, not a warning.

It is an invitation.

I Have No Idea What Happened to the Browser​

This story does not contain the satisfying ending where Chris founded a browser company, became a billionaire, and now owns a private island shaped like a semicolon.

I honestly don't know what happened to it.

Maybe he finished it.

Maybe he abandoned it.

Maybe the code exists on a dead hard drive somewhere.

Maybe one day he looked at the rendering engine and said:

Nope.

Fuck this.

Perfectly reasonable.

That isn't why I remember it.

I remember it because the act itself was insane enough to lodge permanently in my brain.

He looked at something enormous, complicated, foundational, and deeply unnecessary for one person to build.

Then he started building it anyway.

I admired the hell out of that.

While also thinking he was a fucking lunatic.

These two things are not mutually exclusive.

Twenty-Five Years Later​

Fast-forward a quarter century.

I have been writing software for more than twenty years.

I have built products.

Architected systems.

Led teams.

Deployed infrastructure.

Spent enough time around enterprise software to develop several philosophical objections to Jira.

I should know better by now.

Then, for reasons that apparently made sense at the time, I started building a game engine.

Not a game.

A game engine.

Because creating one game would have been dangerously close to behaving like a normal person.

No.

I needed the machinery underneath the game.

Simulation.

Determinism.

Replay.

State.

Systems.

Validation.

All the little pieces that let you build the thing that lets you build the other thing.

At some point I looked at what I had built and the memory of Chris finally wandered back into the room.

Oh.

Oh, you son of a bitch.

I became you.

The Species​

There is apparently a type of programmer who sees a gigantic existing category of software and thinks:

"I wonder how that works."

This is followed almost immediately by the much more dangerous thought:

"I could build one."

Browser.

Compiler.

Operating system.

Database.

Game engine.

At no point does the brain introduce the helpful sentence:

"Perhaps I should go outside."

No.

The brain starts drawing architecture diagrams.

This is how perfectly functional adults disappear for six months and emerge with a package manager.

Nobody asked for the package manager.

There were already package managers.

That was never the point.

The point was that now there is another one.

Then Reddit Arrives​

Of course, once you build something and put it on the internet, a sacred ceremony begins.

Strangers explain the thing you built to you.

Apparently, according to some of the Reddit commentary, this is not how game engines work.

Excellent.

I wish someone had told me before I built the fucking thing.

There were also variations on:

This is a mess.

This is garbage.

That isn't a game engine.

Useful information.

Especially because the engine continued sitting there, stubbornly existing.

Working.

Running deterministic simulations.

Passing tests.

Doing the deeply inconsiderate thing of functioning after strangers had correctly identified that it was impossible.

Software can be rude like that.

Chris Would Probably Understand​

I don't know what Chris is doing now.

I don't know whether he remembers the browser.

I don't know whether he would look at my game engine and say:

"Nice."

Or:

"What the fuck did you build this for?"

Either response would be fair.

But I do know this:

Twenty-five years ago, I watched a brilliant programmer voluntarily walk into a ridiculous technical problem and start building.

I thought he was nuts.

I admired him for it.

And apparently, somewhere along the way, I became the kind of person who does the same thing.

Not because the world desperately needed another game engine.

Not because this was the efficient route.

Not because Reddit approved the architecture.

Because I wanted to know if I could make the machine work.

So I did.

Which leaves only one appropriate thing to say to the younger version of me, standing there watching Chris write his browser:

Careful, motherfucker.

This shit is contagious.


Well... why not?