What does it mean to build perfect software?
Is perfect software, or perfect anything for that matter, even attainable? Or is it a utopian dream?
If perfection is nearly impossible, what options do we have?
You’ve probably heard the old adage “Don’t let perfect get in the way of the good enough,” or something similar.
But what does it mean to be good enough? Well, it’s likely hard to understand what any of this looks like without constant communication with your entire team.
Topics:
• 01:08 – The allegory of the “smart” dishwasher
• 07:39 – We often start building before we know what to do
• 08:32 – Think about the problem in simplest form
• 08:44 – The UX team can help
• 13:06 – “Good enough” is a conversation
• 13:36 – Perfect looks different from Engineers and Designers
• 17:05 – Communication is critical to know what “good enough” is
• 19:52 – Reaching for perfection, within the context, is part of being successful
• 20:59 – How much risk do you want to assume?
• 21:39 – Look down the line for potential risks to “good enough”
• 25:23 – It’s often about intuition and knowing what works
• 33:16 – Perfection can be about anything
• 33:46 – It’s not about being perfect its about finding the perfect balance
—–
Thanks for listening! We hope you enjoyed today’s episode. If you liked what you heard, be sure to like and subscribe wherever you get your podcasts! If you enjoyed today’s episode, please leave a comment and a five-star review. It helps us out a ton.
If you haven’t already, sign up for our email list. We won’t spam you. Pinky swear.
• Check out our website
• Follow us on twitter
• Find us on Facebook
• Subscribe on Google Podcasts
• Subscribe on Apple Podcasts
• Subscribe on Spotify
• Subscribe on Stitcher
Episode thumbnail by Pablò on Unsplash