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.
Well you could at least start with solving everything in 24 hours that can be solved in 24 hours. More often than not such bugs take days, weeks, months not because of time in IDE, but because of backlogs, prioritization, time in test and longer release cycles. Streamlining that sounds mostly a win to me.
Note that a bug fixed in 24hrs is also a bug that doesn't have to be fixed later. I mean the development work has to be done at some point anyway, and this may even save some time discussing and bouncing around the issue.
Speaking as one of those developers, we suggested the topic. We are proud of this!
I've worked at several companies you know (https://www.linkedin.com/in/macneale) - and this is the least toxic company I have ever worked at. Hands down. We take pride in running a tight ship.
ggambetta|1 year ago
"How to fix bugs in 24h", LOL.
lelanthran|1 year ago
rrr_oh_man|1 year ago
Sounds like a hell of a story.
coldtea|1 year ago
Some huge factors are:
- how fast you can test things (e.g. change and re-run test)
- how good runtime (e.g. debugger) and logging visibility you have
- how good (representative) are the test data
In other words, fast ways to "look into" the matter. Usually if you can iterate fast and get a reproduction, you can also solve it fast.
It's much less common that the issue is a big architectural concern that needs total rethinking/refactoring.
lelanthran|1 year ago
icoder|1 year ago
Note that a bug fixed in 24hrs is also a bug that doesn't have to be fixed later. I mean the development work has to be done at some point anyway, and this may even save some time discussing and bouncing around the issue.
nertirs|1 year ago
elaencam|1 year ago
I've worked at several companies you know (https://www.linkedin.com/in/macneale) - and this is the least toxic company I have ever worked at. Hands down. We take pride in running a tight ship.
noir_lord|1 year ago
Some times bugs aren't so much a bug as the anthill.