Poll: How many reported exceptions are in your production environment?

6 points by bradgessler ↗ HN
We'd all love to run a "zero defect" culture but its impossible in a production environment. What is an acceptable number of defects to have in production?

Bring up Airbrake, Exceptional, or whatever tool you use to track this and report your count. How do you stack up against the rest? Vote below and we'll find out!

7 comments

[ 5.0 ms ] story [ 33.2 ms ] thread
Improve phrasing - define exceptions as either programming language "exception" conditions or exceptions to defect management policy, and clarify further (eg. only a subset of pl exceptions are defects or undersireable)
We're completely rewriting our main product and are coming to an end soon-ish. The old code had no useful tests, but there were some that went to our API to test some CRUD. Online.

We now have fixed that and have tests for the more complicated code we have, but we don't really track exceptions. Besides Airbrake and Exceptional, are there any exception trackers for PHP / Symfony2?

90% done, only 90% left to go.

Wouldn't this wildly vary by industry and solution scenario?
Over what time period? We have an average of less than 1 exception per month.

I have also worked on a larger web app that would get thousands of exceptions per day.

I think near 0 is very possible as long as you aggressively attack all exceptions as they show up. Once you start letting some go they tend to pile up exponentially. I keep my phone on me and every time, day or night, that an exception occurs I get notified; it keeps me very motivated to fix problems quickly.