Releasing critical defects that cause 100% breakage for a si...

Troy

npub104zp04wlgddf0w84tj8jul3w75e7ydcuuhsull2etste5040xm2qg285rf

hex

d533e7686b838ba68b2241d4b111088bd3616b7ab579cd83e9a555bfa84fc7e6

nevent

nevent1qqsd2vl8dp4c8zax3v3yr493zyygh5mpddat27wds05624dl4p8u0esprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgs863qh6h05xk5hhr64erew0ch02vlzxuwwtcw0l4v4c9u686hnd4qq7axfv

Kind-1 (TextNote)

2026-03-06T17:11:43Z

↳ 回复 事件不存在

b0a7b38829e70b8909afbfe7bb439c11c341d0d9b78ae1f93eb27e55c3b08bcb...

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.

原始 JSON

{
  "kind": 1,
  "id": "d533e7686b838ba68b2241d4b111088bd3616b7ab579cd83e9a555bfa84fc7e6",
  "pubkey": "7d4417d5df435a97b8f55c8f2e7e2ef533e2371ce5e1cffd595c179a3eaf36d4",
  "created_at": 1772817103,
  "tags": [
    [
      "e",
      "19414e8627631abccb0e6ccc8f66b47cabec542e433ee5dc7d27715553cd52f9",
      "",
      "root"
    ],
    [
      "e",
      "b0a7b38829e70b8909afbfe7bb439c11c341d0d9b78ae1f93eb27e55c3b08bcb",
      "",
      "reply"
    ],
    [
      "p",
      "75d737c3472471029c44876b330d2284288a42779b591a2ed4daa1c6c07efaf7"
    ],
    [
      "p",
      "7fa56f5d6962ab1e3cd424e758c3002b8665f7b0d8dcee9fe9e288d7751ac194"
    ],
    [
      "p",
      "9236f9ac521be2ee0a54f1cfffdf2df7f4982df4e6eb992867d733debcf95b35"
    ]
  ],
  "content": "Releasing critical defects that cause 100% breakage for a significant segment of users is far worse than holding back until those defects are fixed.\n\nThe \"release early and release often, even if it's dogshit\" has never been a good paradigm.\n\nGive 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.\n\nThe 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.",
  "sig": "4ef4cb000524bbdb3911bef0a31bc2c9c8cb4eb7c2b7fc9e69975a83062fdb89ccd4d5833f8e135a4637906d5b44c4af50956cc15b23d9ac76175dcae504e33d"
}