3 ms·
"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.
by 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 agoThat's faster than average
- portaouflop 2y agoAh 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 agoBecause 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 agoThey 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.