korrents

korrents · piece

Is High Quality Software Worth the Cost?

Martin Fowler · 29 May 2019 · martinfowler.com ↗

3 korrents from this piece

Martin Fowler did not write this page.

Every claim below was made in this piece, quoted word for word and numbered in the order the piece makes them, so you can read it there rather than take our word for it. The sentence above each quote is our reading of the claim, not their wording. Each quote was checked against a stored copy of the page at build time; where the two differ, the quote is the fact.

  1. Our reading

    The usual trade-off between quality and cost does not apply to software: high internal quality is the cheaper way to produce it.

    Their wordsWith this article I'll explain that this trade-off does not apply to software - that high quality software is actually cheaper to produce.
    Interesting

  2. Our reading

    Poor internal quality begins to slow a team down within a few weeks, so almost no project is short enough for cutting corners to pay off.

    Their wordsDevelopers find poor quality code significantly slows them down within a few weeks.
    Interesting

  3. Our reading

    Cruft is not carelessness: even the best teams inevitably create it, because the right design is only visible once the software has been built.

    Their wordseven the finest teams will inevitably create some cruft as they work
    Interesting