3 ms·

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 use

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.

tommek4077 2y ago
This might force you to think about quality before shipping stuff. A win for customers.
- dkdbejwi383 2y ago
  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.
  - dgb23 2y ago
    They are apparently a database company though.
lIl-IIIl 2y ago
"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.
- celdon25 2y ago
  That's faster than average
- portaouflop 2y ago
  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?
  - lnxg33k1 2y ago
    Because the rest of the industry is managed by people who don't care about code, and puts people who become coder after a couple of udemy videos in position of charge
  - lIl-IIIl 2y ago
    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.
ben0x539 2y ago
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.
adastra22 2y ago
Well, their website is Dolt Hub.

tommek4077 2y ago

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

dkdbejwi383 2y ago
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.
- dgb23 2y ago
  They are apparently a database company though.

lIl-IIIl 2y ago

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

celdon25 2y ago
That's faster than average
portaouflop 2y ago
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?
- lnxg33k1 2y ago
  Because the rest of the industry is managed by people who don't care about code, and puts people who become coder after a couple of udemy videos in position of charge
- lIl-IIIl 2y ago
  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.

ben0x539 2y ago

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.

adastra22 2y ago

Well, their website is Dolt Hub.