I'm a broke, dumb, nontechnical low 20 something who really just wanted to play something myself and it ended up becoming a large project that's helping me with my personal financed whist being unemployed.
3 things
- ship first, get feedback from users, iterate, stop designing
a lot of people get caught working on features nobody gives a fuck about. I call this "the trance". People want some small mechanic that is cool to them to work and up indefinelty stalling core parts of their project bottlenecking them from shipping, where they coudla worked on that same shit later, dont get stuck in the trance.
2. trust in agentic coding
people are way too egotistical, it can do it better than you, and if it cant, youre using it wrong, trust in the computah.
3. try a donor model
See what people are willing to pay for. The only reason this project is where it is cause one dude donated 2.99 a month, I felt obligated to him and working had a whole new feeling that tickled my ego. Make something niche, ask for donations, listen to your donors advice.
4 (bonus) ask people what youd need to add to your game to make them share it with a friend or pay
chances are if you are nontechnical, agents can code better than you. It's probably more worth it to learn about computer science, system architecture rather then syntax.
Perhaps you would you disagree?
Id like to say the same for most "technical" people, most of my CS buddies have never built anything without an authority figure giving them directions (work/school) and seem to get really threatened at the idea that agentic coding will replace them, often coping with arguments about future, nonexistent issues.
I'm a broke, dumb, nontechnical low 20 something who really just wanted to play something myself and it ended up becoming a large project that's helping me with my personal financed whist being unemployed.
3 things
- ship first, get feedback from users, iterate, stop designing
a lot of people get caught working on features nobody gives a fuck about. I call this "the trance". People want some small mechanic that is cool to them to work and up indefinelty stalling core parts of their project bottlenecking them from shipping, where they coudla worked on that same shit later, dont get stuck in the trance.
2. trust in agentic coding
people are way too egotistical, it can do it better than you, and if it cant, youre using it wrong, trust in the computah.
3. try a donor model
See what people are willing to pay for. The only reason this project is where it is cause one dude donated 2.99 a month, I felt obligated to him and working had a whole new feeling that tickled my ego. Make something niche, ask for donations, listen to your donors advice.
4 (bonus) ask people what youd need to add to your game to make them share it with a friend or pay
find the gap, execute on it, gg.
>it can do it better than you
>nontechnical
Congrats for the success. Hoping you don’t run into major issues. The donation model idea is interesting
chances are if you are nontechnical, agents can code better than you. It's probably more worth it to learn about computer science, system architecture rather then syntax.
Perhaps you would you disagree?
Id like to say the same for most "technical" people, most of my CS buddies have never built anything without an authority figure giving them directions (work/school) and seem to get really threatened at the idea that agentic coding will replace them, often coping with arguments about future, nonexistent issues.
Are there issues you foresee me running into?