4 ms·
I enjoyed the book _Leprechauns of Software Engineering_ which did track down all the chains of citations to find where the original work was misunderstood or e
by tibbetts 5y ago
I enjoyed the book _Leprechauns of Software Engineering_ which did track down all the chains of citations to find where the original work was misunderstood or even nonexistent. I would bet that it covers most or even all of these citations, but I’m not taking the time to pull it out and cross reference. https://leanpub.com/leprechauns https://leanpub.com/leprechauns
- jdlshore 5y agoYes, and it’s worth noting that Hillel was referring to _Leprechauns_ when he talked about the cost to fix claim.
- SloopJon 5y agoOne of the most recent citations (Shull et al. 2002) is freely downloadable: https://www.computer.org/csdl/proceedings-article/metrics/2002/13390249/12OmNzfXau9 https://www.computer.org/csdl/proceedings-article/metrics/20... Its own citations may not be satisfying, but I find it nevertheless interesting. Here's the summary of the eWorkshop discussion of "Effort to find and fix": > A 100:1 increase in effort from early phases to post-delivery was a usable heuristic for severe defects, but for non-severe defects the effort increase was not nearly as large. However, this heuristic is appropriate only for certain development models with a clearly defined release point; research has not yet targeted new paradigms such as extreme programming (XP), which has no meaningful distinction between "early" and "late" development phases.