A Quantitative Analysis into the Economics of Correcting Software Bugs

Using a quantitative study of in-house coding practices, we demonstrate the notion that programming needs to move from “Lines of Code per day” as a productivity measure to a measure that takes debugging and documentation into account. This could be something such as “Lines of clean, simple, correct, well-documented code per day”, but with bugs propagating into the 6th iteration of patches, a new paradigm needs to be developed

Never miss a story from Craig Wright (Bitcoin SV is the original Bitcoin)