Watts Humphreys was probably the first to the idea of scaling development processes down, rather than up, arriving in the 90s at the Personal Software Process.
The PSP is very data-intensive. You're meant to log pretty much everything you do.
For example, you log your mistakes. Missed a semicolon? Log the mistake. Typo in a variable name? Log the mistake. Critical misunderstanding of how a library works? Log the mistake.
After a while you use your data to correct your common errors with ... checklists! And other tools and practices, of course, but checklists are a big part of the PSP.
It's worth reading A Discipline for Software Engineering, even if you never apply it.
Comments
This is essentially describing a "process".
Except instead of emphasizing team-level details, it calls for an emphasis on code-level details. I really like this idea.
Watts Humphreys was probably the first to the idea of scaling development processes down, rather than up, arriving in the 90s at the Personal Software Process.
The PSP is very data-intensive. You're meant to log pretty much everything you do.
For example, you log your mistakes. Missed a semicolon? Log the mistake. Typo in a variable name? Log the mistake. Critical misunderstanding of how a library works? Log the mistake.
After a while you use your data to correct your common errors with ... checklists! And other tools and practices, of course, but checklists are a big part of the PSP.
It's worth reading A Discipline for Software Engineering, even if you never apply it.