[dsr_]

IN the apartment building, we have a known problem, a high severity attached to it, an unacceptably high incident rate, and no idea of the exact conditions necessary to replicate it.

At this point I would do two things:

1. log all the things.

2. find me my top QA person, the one who can find bugs that nobody has yet reported. Put her on it.

OK, everybody knows that logging is good. And everyone knows that QA is good.

What I have found, though, is a number of companies who think that QA is best done by the developer who wrote the feature... and I think they are absolutely wrong in every sense, except possibly short-term economics. Having someone do QA who has none of their ego invested in the code is essential.