loading...

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

FULL DISCUSSION
 

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 knowing where to draw the line (i.e. it's ok to ship with bug X, we'll fix that in the next release but it's not ok to ship with bug Y, it's dangerous and needs to be addressed now). There are always code reviews, and lots of testing to try and make sure nothing slips through.

My problem is with my side projects. Because I can't come up with the perfect idea, I'm paralyzed by indecision and can't seem to get started. I'll keep trying and see if I ever decide to actually do something; but reading this was helpful. It's always nice to know that others have struggled with the same problems, and found a way to overcome them.

 

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