15. Pragmatic Craftsmanship
There is an assumption that quality takes time. Managers and developers believe they need to choose between expensive well-crafted code that takes a long time to write or cheap average code that is delivered faster. Unfortunately, cheap average code that is delivered faster usually triumphs over well-crafted code.
In this chapter we bust the myth that quality is expensive. We will also discuss, with examples, what pragmatic craftsmanship really means.
Quality Is Always Expected
I’ve yet to meet a person who wouldn’t want quality if quality were inexpensive or if quality didn’t need to be considered as a trade-off for something she judged more important at some point in time—like time to market or cost. No manager ...
Get The Software Craftsman: Professionalism, Pragmatism, Pride now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
