Thread

Loading the complete thread in the background. This saved snapshot is available now. Refresh

1. flohofwoe · 1790237800 · focus · HN ↗

   It's a good thing to have the "this post was AI generated" signal in the first sentence, saves me a lot of time to read the post ;)
2. heyjstn · 1790238174 · focus · HN ↗

   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
3. stevoski · 1790239366 · focus · HN ↗

   > 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.)

   1. flohofwoe · 1790243521 · focus · HN ↗

      So basically "move fast and break things", hardly new or controversial in the tech bro sphere ;)

      1. Malcx · 1790252660 · focus · HN ↗

         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)

      2. stevoski · 1790259650 · focus · HN ↗

         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.

      3. MikeHer · 1790320597 · focus · HN ↗

         [dead]

Unofficial Hacker News client; not affiliated with Y Combinator.