Bugs are an inevitable part of complex software and aiming for complete bug-free perfection is not only unrealistic, but it hinders progress and product delivery.In this episode of Rework, host Kimberly Rhodes sits down with 37signals founders, Jason Fried and David Heinemeier Hansson to discuss why you need to be realistic about bugs in software development. Listen in as David and Jason offer a behind-the-scenes look at the two-tiered approach to handling bugs in their software at 37signals and their triage plan for determining which should be fixed, when, and by whom.Tune in to uncover strategies to manage your customers' expectations while dealing with bugs WITHOUT deviating from your product roadmap Check out the full video episode on YouTubeShow Notes: [00:00] - Kimberly opens the show and shares the topic for discussion, that bugs in software are normal. [00:27] - David shares why you need to be realistic about bugs in software development.[01:18] - Bugs, a natural side effect of software. [02:08] - What makes users abandon a piece of software (hint: it’s usually not a few bugs)?[05:26] - The two-tiered (non-emotional) approach to handling the vast spectrum of bugs in complicated pieces of software.  [06:13] - When is a “bug” not a “bug”? [07:00] - Handling customer expectations without screwing up your product roadmap.  [07:52] - You need a filter: the double-edged sword of founders operating in customer support.  [08:32] - David shares a behind-the-scenes look triage at 37signals.  [09:31] - The novel QA approach of the Toyota production line that 37signals tries to emulate. [11:37] - Jason shares the difference between the software and auto industries when fixing production problems. [12:37] - Yes, quality matters, but perfect never gets shipped. [14:30] - So how do we build useful, meaningful software? [15:21] - Breaking out of bad bug thought patterns so you can keep making software of value. [16:47] - Who oversees fixing the bugs at 37signals—the methods they use to determine what gets fixed, when, and by who. [20:08] - Cleaning up the tech debt: the vital importance of a measured, mature way of scheduling things. [21:09] - Don't create ****** software—it can’t be fixed. [23:55] – Jason discusses the idea an organization might be a bigger problem than just a bug in the software.[24:44] - Why you should never become "too big" to listen to your customers. [26:28] – For more, check out our Dev.37signals blog, where the 37signals developers write about some of their processes.[26:45] - Rework is a production of 37signals. You can find show notes and transcripts on our website. Full video episodes are also available on Twitter and YouTube. If you have questions for David and Jason about a better way to work and run your business, we’d love to answer them. Leave your voicemails at 708-628-7850 or send an email. Links and Resources:From David’s HEY World: Software has bugs. This is normal. Dev.37signalsIt Doesn’t Have to Be Crazy at Work  Sign up for a 30-day free trial at Basecamp.comHEY World | HEY 37signals on YouTubeThe REWORK podcastThe 37signals Dev Blog@37signals on Twitter