Every game we've made since 2016 runs on a backend I wrote myself. This is how it works, and why I moved it to C# this year.

16 points•MikeHer•9 days ago•6 comments•

6 comments

flohofwoe7 days ago
It's a good thing to have the "this post was AI generated" signal in the first sentence, saves a lot of time ;)

(although tbh, I'm starting to wonder if people subconsciously warp their own writing style when they stare at Claude output all day)

heyjstn7 days ago
I'm tired of reading the Claude-ish generated visualizations, it's fine that you're using AI to write the post but at least please trying to polishing the article if you really care
stevoski7 days ago
> I want to build a feature in the morning and have it live in the afternoon, and anything that gets in the way of that has to go.

Love this!

The philosophy behind how the author runs his app is very much like mine - go for simple, proven tech that you know really well.

(For the people dismissing the article because AI, you are missing out on a good read.)

flohofwoe7 days ago
So basically "move fast and break things", hardly new or controversial in the tech bro sphere ;)
Malcx7 days ago
With game dev, especially live ones with an active player base you do _not_ want to break things if you're a small studio.

But moving fast and shipping features quickly is a killer trait those small teams can use to be better than the big studios. (who ironically seem to ship slow and still break things)

stevoski7 days ago
Reading back, I can see how you interpreted that way.

But the quote from the article is in the context of a 1-person dev team, and how by keeping things really simple so that it is indeed _possible_ to build a feature in the morning and have it live in the afternoon.

Read the full thread on Hacker News →

Related stories