I agree with a lot of the points in this but not the conclusion. One thing I would like to emphasize: You don't write software for software's sake. You write i

I agree with a lot of the points in this but not the conclusion. One thing I would like to emphasize: You don't write software for software's sake. You write it to solve a problem, generally a business problem. If your software has a problem, that may also be a business problem. Don't make IT support solve business problems. Make the business solve them, and give the business tools to solve them. Obviously you won't get there with the first release of your software, but it is the goal. If you find a problem in the logs, ask yourself: Am I masking a problem that the business needs to solve themselves? Does the software need to surface this?