How many (and what type) bugs you can afford to let slide really depends on your users' needs:
As a biomedical technology, we have to demonstrate the scientific accuracy of the product we ship. We also have to be aware of the consequences of bugs to our users. While Facebook users may not mind a slightly finicky widget, laboratory technicians are much more sensitive.
I'm all for rapid iteration and product development, but I think it's important to ship things that are context-appropriate. I also feel that there's substantial, if intangible, value to being proud of what you ship.
I worry that a culture of shipping somewhat-broken things may end up doing us harm.
The concept of shipping asap does not have to mean a complete rollout or the entire biomedical industry, but shipping to a production system that a certain group of users USE for actual work.
Shipping® also encourages a single source of truth for the development team to work from. The master branch is really just another branch when a project does not push that master immediately to production.
Comments
How many (and what type) bugs you can afford to let slide really depends on your users' needs:
As a biomedical technology, we have to demonstrate the scientific accuracy of the product we ship. We also have to be aware of the consequences of bugs to our users. While Facebook users may not mind a slightly finicky widget, laboratory technicians are much more sensitive.
I'm all for rapid iteration and product development, but I think it's important to ship things that are context-appropriate. I also feel that there's substantial, if intangible, value to being proud of what you ship.
I worry that a culture of shipping somewhat-broken things may end up doing us harm.
That was my first thought as well. I make unmanned helicopters -- it's cool to ship a half-ton flying machine with software bugs, right?
But the article did at least make it clear that the advice was targeted at smaller SaaS providers. Depending on the users needs, that might be okay.
The concept of shipping asap does not have to mean a complete rollout or the entire biomedical industry, but shipping to a production system that a certain group of users USE for actual work.
Shipping® also encourages a single source of truth for the development team to work from. The master branch is really just another branch when a project does not push that master immediately to production.