> This sounds so nice in theory. All those pesky developers refusing to fix their horrible code. This might be the niche I'm working in, but that does not soun

> This sounds so nice in theory. All those pesky developers refusing to fix their horrible code. This might be the niche I'm working in, but that does not sound all that unreasonable to me; I certainly know the type. At first, there is a debate whether there really is a bug (instead of giving a trained user and the according support staff the benefit of the doubt), then there is a debate whether the bug should really be fixed or the thing is delayed at nauseam ("need more information" without even having skimmed the damn code at least once). And when the business side finally puts their foot down, the defect is "fixed" with some minimalistic, ad-hoc duct-tape solution that guarantees that five other bugs will pop up in the future because of it. So while I agree with your second point, that doesn't invalidate the first. These kinds of devs actually do exist (with various degrees of intensity, of course). I'm not sure if the archetype is really fit support work, though.