21–30 of 45 posts
Saying that your developers will solve every problem in 24 hours seems like a toxic pr move.
Why optimize for this? Some of the worst jobs I’ve had were the ones where a PM would say “drop whatever sprint items you’re working on and immediately context switch to this bug”. Sounds like this is their regular day? And what happens if a bug comes in Friday @ 4pm?
From the article it sounds like a completely different game than what you mention, which I also experienced at times.
Reminds me of my stint in software. We could easily to these numbers as well. Until we outsourced code production to a country halfway round the globe. Completely changed the dynamics from solving interesting problems in nicely written code, to chasing people around you've never met and never will to fix bugs in 1000+ lines functions, while you know it's an exercise in futility as no doubt there will be lots and lots…
"But they're cheaper!"
"Just fix the bugs!"
Etc...
It's. Just. Not. Possible to convince anyone that it's not like hiring a recent immigrant to clean your yard. Sure, their English might not be so good, but they can hold a broom, right? No big deal! Worst case, if they miss a spot, you can just point to it and they'll fix it.
The destruction of code quality is an invisible, insidious thing that can end billion-dollar companies while management whistles all the way to the bank collecting their bonus cheques for yet another awesome quarter.
Why optimize for this? Some of the worst jobs I’ve had were the ones where a PM would say “drop whatever sprint items you’re working on and immediately context switch to this bug”. Sounds like this is their regular day? And what happens if a bug comes in Friday @ 4pm?
It also should come with a culture of treating bugs like you do a production incident: You do retrospectives and figure out what you can change to your process to reduce the likelihood of the same type of bug happening again. You likely also have a more extensive suite of tests to prevent regressions.
Bug resolution time depends on how familiar a developer is with the system, how complex the issue is and how impactful the bug is. Not everything can be solved in 24 hours. Not everything has to be solved in 24 hours. Saying that your developers will solve every problem in 24 hours seems like a toxic pr move.
"How to fix bugs in 24h", LOL.
Reminds me of my stint in software. We could easily to these numbers as well. Until we outsourced code production to a country halfway round the globe. Completely changed the dynamics from solving interesting problems in nicely written code, to chasing people around you've never met and never will to fix bugs in 1000+ lines functions, while you know it's an exercise in futility as no doubt there will be lots and lots…
It's physically impossible to convince non-technical managers (or technical managers too far removed from the code) that this is always a one-way decision that cannot ever be remediated. Inevitably, the codebase will corrode and decay until its Git repo becomes a superfund site and has to be fenced off with razor wire festooned with warning signs to keep the newbies away. "But they're cheaper!" "Just fix the bugs!" E…
Assuming that wasn’t the point all along.
Bug resolution time depends on how familiar a developer is with the system, how complex the issue is and how impactful the bug is. Not everything can be solved in 24 hours. Not everything has to be solved in 24 hours. Saying that your developers will solve every problem in 24 hours seems like a toxic pr move.
Yes, that was my reaction as well. I'm still traumatized by an insidious bug in a distributed system that took me around 3 months of nearly exclusive work to diagnose and fix (one-line fix, of course). ENG-168. Never forget. "How to fix bugs in 24h", LOL.
Sounds like a hell of a story.
Bug resolution time depends on how familiar a developer is with the system, how complex the issue is and how impactful the bug is. Not everything can be solved in 24 hours. Not everything has to be solved in 24 hours. Saying that your developers will solve every problem in 24 hours seems like a toxic pr move.
Some times bugs aren't so much a bug as the anthill.
Hopefully they pay a decent on-call allowance in the event a bug is reported over the weekend or a public holiday.