loading...

re: Prioritization for Perfectionists, or: How I Learned to Stop Worrying and Love the Non-Perfection VIEW POST

TOP OF THREAD FULL DISCUSSION
re: Great article! I'm in the company that needs to deliver high quality code (it's typically safety critical), and there we've done a good job of know...
 

Thank you, James, nice to know you liked the article!

I know exactly how you feel. Your approach works perfectly well in your current company, but for some "less important" projects it's really hard to switch this mindset.

Yes, you need to be brave and decide to release, even if it's not perfect. You'll feel very good about that, I promise! You'll get a lot of endorphins :).
Also, the earlier you release, the more user feedback you'll get, and the better you can move forward with your project. The user feedback is both reassuring (people actually like your thing!) and helpful (they tell you what features they'd like, and you can focus on them first).

Code of Conduct Report abuse