I'm a small business programmer. I love solving tough problems with Python and PHP. If you like what you're seeing, you should probably follow me here on dev.to and then checkout my blog.
We've been using this checklist at my work for a couple of years and it really works for us. We find a only a handful of minor errors in production each year (which is a fraction of what we found before we used this checklist).
Watts Humphrey published extensively zero-defect software. I wrote a summary here.
But, even if you don't want anything to do with PSP (and most people don't), chapter 8 of PSP: A Self-Improvement Process for Software Engineers lays out the economic case for producing high quality software. Spoiler: it's almost always worth the effort for software that's going to be around for a long time.
Great post, Jonathan. Zero-defect software is a worthwhile goal (one that I've been pursuing for the last couple of years).
Here's my code review checklist.
We've been using this checklist at my work for a couple of years and it really works for us. We find a only a handful of minor errors in production each year (which is a fraction of what we found before we used this checklist).
Watts Humphrey published extensively zero-defect software. I wrote a summary here.
But, even if you don't want anything to do with PSP (and most people don't), chapter 8 of PSP: A Self-Improvement Process for Software Engineers lays out the economic case for producing high quality software. Spoiler: it's almost always worth the effort for software that's going to be around for a long time.
Thanks for sharing, Blaine! That writing by Humphrey looks very interesting. I'll certainly read up on it.