Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

You're doing this because you're working on toy projects with no real stakes. You overcomplicate because you can afford to.

Establish a forcing function in the form of users. Onboard them and include a way for them to report bugs (provide them with an issue template) and also maybe add a Slack workspace for the project. This will do two things:

- Bring issues you were not aware of to your attention.

- Prioritize your backlog with frequency/severity: by the time the fifth user complains about something you were aware of (frequency), you'll drop whatever non-essential thing distracting you and get to fixing that issue. By the time something really bad happens once (severity), you get to work on it as soon as possible.



I can't get to the stage where I have users


Could you elaborate, please?


I don't reach a stage where something is running. E.g. I have half-broken login page (with backend services) instead of actual image hosting.


Precisely. Get users to your product and you'll reach the stage of finishing and getting working things out of the door.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: