A first-time game dev shared his flopped demo on HN and asked for resources to learn game design. 140 comments later, the advice converges from every direction: stop trying to learn design from content and start finishing small games.
The recurring lessons, from veterans who actually shipped:
- Ship small, ship many. DOOM was Romero’s 100th game. Your gems sit at the back of the stack — you have to pop the shit ones first.
- Clone before you create. Reproduce a tiny mechanic from a game you love and throw it away. Duplicate a proven mechanic like Tetris or Balatro and perfect it until you are bored — then add one tweak.
- Study board games. Ruthless constraints force designers to justify every element. A video game should be pitchable as succinctly as a board-game teach video.
- Ask early, in person. Show devs before you are ready. Start with five trusted testers, iterate until they are excited, then scale to 20, then 100. Never debut in a large public venue.
- Kill the signup wall. Players bounce the moment they are asked to create an account. Drop them straight into the fun; ask for the signup only after they are hooked.
- Design is the craft. If you are a programmer, game design is not a side skill — it is the product. Work with someone confident in design instead of expecting to invent it from books.
- Clean up your information diet. People with time to podcast and build personal brands mostly are not building anything. Makers are too busy to post.
The thread’s real message: a failing first demo is not the problem — it is the fastest feedback you will ever get. The fix is not another book, it is a smaller game, finished, in front of five people who will tell you the truth.