IMO the hardest step for aspiring (commercial) indie game developers is learning to finish games consistently and efficiently - to move past game jams and prototypes but also avoid getting mired in a single project for years without end. It's a tiny sweet spot that's hard to hit.
One piece of advice is to try and avoid falling in love with your development tools over the game you're building them for. You will find time and time again that successful indie games are often built with crude tools and/or messy code. Just enough to get the job done.
I've also come to believe that if you show off your game and receive a tepid response, it's generally better to try and finish the game *faster* and move on instead of extending the development to try and fix what is probably an issue at the core.
Non-dev feedback is usually the best way to find out if your core ideas are working. Other game developers are more likely to focus on specific criticisms but try and leave you feeling positive and optimistic overall. It's helpful and motivating but can be dangerous for new devs.
To sum up, I think it's really important to learn how to finish games reliably; to see the beginning, middle, and end of development lots of times; to find the intersections of what you and other people enjoy; to learn how to skirt or overcome the many mental traps along the way.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
