Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

How to fix bugs in 24 hours or less

dolthub.com

Post reply on HN
Print view View original

41–45 of 45 posts

Re: How to fix bugs in 24 hours or less

#41

Post by lelanthran »

ggambetta wrote: post #26
nertirs wrote: post #21

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.

That is ... impressive! My longest was 3 weeks, working exclusively.

Re: How to fix bugs in 24 hours or less

#42

Post by elaencam »

nertirs wrote: post #21

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.

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.

Re: How to fix bugs in 24 hours or less

#43

Post by lIl-IIIl »

portaouflop wrote: post #36
lIl-IIIl wrote: post #7

Earlier quoted context omitted.

"Your code has to be good enough that you don't get a large flow of bugs." The article also says it took them a year to get to this point.

Ah it’s that easy, just write good code without bugs. I wonder why the rest of the industry continues to produce so many bugs, didn’t they figure this out?

They are not writing code without bugs. But the rate of incoming bugs varies from project to project. For mature projects without a lot of churn the bug rate decreases over time.

They may also be in a position where they can afford to delay releasing a feature until all bugs are fixed. Most teams on the other hand ship with known bugs, because a feature with bugs today will make more money than a feature without bugs tomorrow.

Re: How to fix bugs in 24 hours or less

#44

Post by ggambetta »

lelanthran wrote: post #41
ggambetta wrote: post #26

Earlier quoted context omitted.

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.

That is ... impressive! My longest was 3 weeks , working exclusively.

Turns out it was only 2 weeks, but it felt like 3 months :) See my other comment.

Re: How to fix bugs in 24 hours or less

#45

Post by rrr_oh_man »

ggambetta wrote: post #35
rrr_oh_man wrote: post #28

Earlier quoted context omitted.

Can you elaborate? Sounds like a hell of a story.

At a previous company, we were in the early stages of building a massively distributed simulation platform that would power MMOs and government/military simulations. The platform was written in Scala and used Akka extensively (because of reasons). We had a test environment that spun up a decently big game world, and had a bunch of bots run around and do things. It would run overnight. At some point it was discovered…

That was even better than expected.

Thanks for sharing!

Post reply on HN