But to add up to my previous comment - only a few people get to implement new stuff each year, they don't test their code and fall under very tight deadlines, so they produce buggy stuff. This generates tones of new bugs constantly tracked by QA (QA doesn't fix anything, they just report problems), bugs quickly pill-up in Radar and developers are already assigned onto something else. Most of the bugs reported by customers are duplicates... they're usually already tracked, either not assigned yet or simply lower priority than something else. So what it the problem? Well, everything I mentioned ;)
> Management doesn't even reward bug fixing
I think that's the moral of the story. It's not that developers are childish, stamp their feet, and refuse to do bugfix work; it's that they're incentivized to not do it.
Really? I've never experienced that in the workplace. However, I'm not that widely travelled and not in SV, so I guess I'd be "unsurprised but depressed" to learn that this degree of idiotic entitlement is common. And idiotic is exactly what it is: truly quality software is the product of lots and lots of bugfixing. It's like the "10% inspiration/90% perspiration" thing, but for initial development and bugfix/gradual improvement work. Especially on huge (OS-sized) software, people hiring on should not be surprised that this is the bulk of their day-to-day.
I get that greenfield development is more fun up front. I just (perhaps naïvely) hope that most professionals understand that a) "fun" and "good for the product" aren't the same thing, and b) that it can also be very personally rewarding to spend a long time fixing bugs (yours or others') and see the quality of/user happiness with a product noticeably increase.
Also, I think being able to say "I fix bugs to maintain an operating system used by millions" is at least as rewarding as being able to say "I make buggy websites for startups whose marketing buzz reaches millions".