My survey of the computer science literature suggests there are only two economical ways to achieve extremely low defect rates (< 1 defect per KLOC). The first way is to follow the Personal Software Process (PSP), which was created by Watts S. Humphrey at CMU. The second way is to use languages and tools that make it difficult to introduce errors into your code in the first place and easier to detect errors if you do manage to get some into your code. In this post I’m going to briefly discuss these two options and how I plan to explore them to become a better software developer.
Month: May 2018
Top Posts
- Safety-Critical Software: 15 things every developer should know
- Optimal pull request size
- High Integrity Sumobot: Build Instructions
- Steve McConnell's Classic Software Mistakes Revisited
- How to Crush it at the Start of Your New Developer Job
- Is Uncle Bob serious?
- Why I can't recommend Clean Architecture by Robert C. Martin
- A code review checklist prevents stupid mistakes
- The ONE chart every developer MUST understand
- How to get hired as a team lead