Gregory Maxwell [ARCHIVE] on Nostr: 📅 Original date posted:2011-09-19 🗒️ Summary of this message: Fixing bugs ...
📅 Original date posted:2011-09-19
🗒️ Summary of this message: Fixing bugs alongside improvements can introduce new bugs, making it risky to stay on top of bugfixes. New bugs can outweigh the benefits of fixing one.
📝 Original message:On Mon, Sep 19, 2011 at 11:00 AM, Luke-Jr <luke at dashjr.org> wrote:
> The problem with the current development model is that bugfixes are done
> alongside improvements, and code changes *always* have the potential to
> introduce new bugs, no matter how careful anyone is. So to stay on top of
> bugfixes right now implies risking new bugs being introduced. What good is
> getting one bug fixed, if it comes with 20 new yet-to-be-discovered bugs?
Bug fixes also introduce bugs. Considering the fairly small number of new
features added, I'd take a bet that most of the more recently introduced
bugs were the result of fixes not features.
🗒️ Summary of this message: Fixing bugs alongside improvements can introduce new bugs, making it risky to stay on top of bugfixes. New bugs can outweigh the benefits of fixing one.
📝 Original message:On Mon, Sep 19, 2011 at 11:00 AM, Luke-Jr <luke at dashjr.org> wrote:
> The problem with the current development model is that bugfixes are done
> alongside improvements, and code changes *always* have the potential to
> introduce new bugs, no matter how careful anyone is. So to stay on top of
> bugfixes right now implies risking new bugs being introduced. What good is
> getting one bug fixed, if it comes with 20 new yet-to-be-discovered bugs?
Bug fixes also introduce bugs. Considering the fairly small number of new
features added, I'd take a bet that most of the more recently introduced
bugs were the result of fixes not features.