3 ms·
I think we're on the same page. I was simply highlighting things I witnessed from my past experience. Bugs (in Mac OS) get really nasty sometimes and frustratin
by bsvalley 9y ago
I think we're on the same page. I was simply highlighting things I witnessed from my past experience. Bugs (in Mac OS) get really nasty sometimes and frustrating for the most part. It is brain consuming and the reward isn't always worth the energy spent. Management doesn't even reward bug fixing unlike the "new" stuff. Ask any dev from that specific team (or even iOS team) to fix bugs for a whole year and you'll see the reaction. Some actually do because of a "lower" global performance at work. You can easily get assigned on bugs over "new" stuff if you don't hustle 24/7 but that's a whole new topic :)
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 ;)
- zbentley 9y agoI think we agree as well; my reply was meant to speculate on whether anti-maintenance sentiment comes from developers or higher up (culture etc.). > 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.