Manage episode 235264649 series 2355351
We look at Martin Fowler’s article titled “Is High Quality Software Worth the Cost?” We discuss the gives and takes of writing good software and managing technical debt. We look at misconceptions around software quality and cost, and how planning and blueprinting (architecting) up front can save teams money in the future. Moreover, we look at how good software offers teams a competitive advantage over others due to the ability to ship new features quickly and confidently.
- Who Martin Fowler is
- On Martin Fowler's article titled, "Is High Quality Software Worth the Cost?" - Are we used to a trade-off between quality and cost - Software quality means many things - Internal quality does not matter to customers - Internal quality makes it easier to enhance software - Customers do care that new features come quickly - Visualizing the impact of internal quality - Even the best teams create cruft - High quality software is cheaper to produce
Links: Is High Quality Software Worth the Cost? - Martin Fowler - https://martinfowler.com/articles/is-quality-worth-cost.html Martin Fowler - https://martinfowler.com/ Betteridge's law of headlines - Wikipedia - https://en.wikipedia.org/wiki/Betteridge%27s_law_of_headlines