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

11–20 of 45 posts

Re: How to fix bugs in 24 hours or less

#11

Post by ben0x539 »

portaouflop wrote: post #5
kristopolous wrote: post #2

They mean wall time and not work time. That's pretty aggressive

It’s not only unreasonable - who expects/needs this? - is also unsustainable. What happens if 5 bugs get filed on a Friday. Might be good when you have few users in the beginning but long term I don’t see it happening.

I mean, it's a way to set priorities. Even it turns out not to be an iron clad guarantee, having taken that pledge means when people end up taking too much time fixing bugs, it's already consensus that that's not acceptable, and it'll presumably be much easier to make the case to allocate resources to address it.

Re: How to fix bugs in 24 hours or less

#12

Post by dkdbejwi383 »

tommek4077 wrote: post #6
portaouflop wrote: post #5

Earlier quoted context omitted.

It’s not only unreasonable - who expects/needs this? - is also unsustainable. What happens if 5 bugs get filed on a Friday. Might be good when you have few users in the beginning but long term I don’t see it happening.

This might force you to think about quality before shipping stuff. A win for customers.

At a certain point it'll hamper ability to ship features quickly, as you go from having to think about the 80% of uses cases, to spending a significant chunk of time anticipating and fixing all kinds of very unlikely edge cases.

I guess it's preference, but I'd rather ship quickly and cover most of my users, and respond to any bugs that do surface (and there's every chance they won't) for obscure issues that probably won't really impact revenue.

Re: How to fix bugs in 24 hours or less

#13

Post by adastra22 »

portaouflop wrote: post #5
kristopolous wrote: post #2

They mean wall time and not work time. That's pretty aggressive

It’s not only unreasonable - who expects/needs this? - is also unsustainable. What happens if 5 bugs get filed on a Friday. Might be good when you have few users in the beginning but long term I don’t see it happening.

Well, their website is Dolt Hub.

Re: How to fix bugs in 24 hours or less

#14

Post by dgb23 »

dkdbejwi383 wrote: post #10

Hopefully they pay a decent on-call allowance in the event a bug is reported over the weekend or a public holiday.

Well yes. This isn’t for everyone. The company has to pay a premium and the workers have to sacrifice time.

But if you make these sorts of promises you have to make sacrifices.

I think it’s refreshing to see this kind of thing though.

Re: How to fix bugs in 24 hours or less

#15

Post by dgb23 »

dkdbejwi383 wrote: post #12
tommek4077 wrote: post #6

Earlier quoted context omitted.

This might force you to think about quality before shipping stuff. A win for customers.

At a certain point it'll hamper ability to ship features quickly, as you go from having to think about the 80% of uses cases, to spending a significant chunk of time anticipating and fixing all kinds of very unlikely edge cases. I guess it's preference, but I'd rather ship quickly and cover most of my users, and respond to any bugs that do surface (and there's every chance they won't) for obscure issues that probably…

They are apparently a database company though.

Re: How to fix bugs in 24 hours or less

#16

Post by andreareina »

dgb23 wrote: post #14
dkdbejwi383 wrote: post #10

Hopefully they pay a decent on-call allowance in the event a bug is reported over the weekend or a public holiday.

Well yes. This isn’t for everyone. The company has to pay a premium and the workers have to sacrifice time. But if you make these sorts of promises you have to make sacrifices. I think it’s refreshing to see this kind of thing though.

Frequently the people making promises aren’t the ones making sacriices.

Re: How to fix bugs in 24 hours or less

#17

Post by Stem0037 »

Pressure to resolve issues hastily could lead to suboptimal, band-aid solutions rather than thoughtful, robust fixes that address root causes. The relentless pace may be unsustainable and lead to engineer burnout.

On top of all that, if not managed carefully, the 24-hour guarantee could perversely incentivize customers to classify all requests as "bugs" to get faster service, blurring the line with genuine feature requests.

Re: How to fix bugs in 24 hours or less

#19

Post by celdon25 »

KMnO4 wrote: post #3

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?

On-call rotations are pretty common in the industry, I don't see any mention in the article of the entire team being on-call 24/7.

Re: How to fix bugs in 24 hours or less

#20

Post by celdon25 »

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

Earlier quoted context omitted.

It’s not only unreasonable - who expects/needs this? - is also unsustainable. What happens if 5 bugs get filed on a Friday. Might be good when you have few users in the beginning but long term I don’t see it happening.

"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.

That's faster than average
Post reply on HN