I mean, take it to it’s logical extreme, I make an app that does X, but every time you start it, it crashes.

I doubt it’s going to be long before my product fails, bugs are affecting the value users derive from it to an extreme degree, past what they can overlook.

I honestly can’t even think of a real-world example off the top of my head though.

But that’s probably just a testament to how badly you need to screw up for bugs to be the actual reason a product fails, and not some external factor that’s possibly exacerbated by bugginess

>>> I make an app that does X, but every time you start it, it crashes.

Then it doesn't do X

Buggy code is a huge drag on any codebase and any business built on that codebase - absolutely.

But if you list all the things you think you MUST fix in a codebase, they are all things that make you as a developers life harder.

The bugs that a user sees are the ones that take away the value they get - the ones you see are the ones that make it harder as a developer to work on the code base - they are rarely the same bugs

this is the cause of most tension

That’s pretty much my point...

i misunderstood your point - it is a bit clearer on a reread

For a long time Pandora was much better written than Spotify. Pandora was stable and performant and Spotify always slowed down my phone and would crash it consistently sometimes in way that required a phone restart.

Spotify won because they had a large selection of music which was more important than the occasional frustrations.

Do you remember Facebook Chat when it first came out? Barely worked. People still used it all the time.

Twitter used to crash all the time.

Edit: from 'Twitter?' to the above.

Windows 3.0 was very successful, but it crashed a lot.

Early Android.