OverviewExploreTrending
Nostr Archives
OverviewExploreTrending
Troy7d ago
Releasing critical defects that cause 100% breakage for a significant segment of users is far worse than holding back until those defects are fixed. The "release early and release often, even if it's dogshit" has never been a good paradigm. Give weight to defect classifications, keep track of your weighted defect count prior to release, then go into "no new features" mode until the score is low enough AND there are no critical high-priority defects. It's not even challenging to do. It just takes being patient while being excited to release new features. The other option is to have a reputation for releasing garbage, which results in new people not even installing to check it out. Or worse, dedicated users swearing to never install software you make ever again. That's how Norton Utilities went from being the de-facto software for all admins in the PC world, to total bankruptcy.
💬 2 replies

Thread context

Root: 19414e862763…

Replying to: b0a7b38829e7…

Replies (2)

Niel Liesmons7d ago
:110percent:
0000 sats
JOE2o7d ago
I think it's not so much that, it's more a fundamental cake and eat it to situation with regard to what is actually being attempted here. You cannot have stateful and stateless at once, managed and unmanaged, and if you try then every release will have a critical issue, you're simply shifting critical issues around.
0000 sats