I have a template I apply before releasing a program at work, most of which is a header of documentation boilerplate. I included a “Bugs & Limitations” section, and prior to testing I list the limitations I can forsee that (I believe ;) fall outside anticipated usage.

More than once, just the exercise of writing this section has ”encouraged’ me to go back and make changes to the program, just so I can remove a limitation comment from the documentation. Not every limitation gets removed, especially for small, limited usage cases, and I find that putting in warnings for future maintainers provides an immediate sense of relief for some part of my release anxiety. If I’m unable to dump most of this anxiety by documenting or testing then it isn’t ready for release.

OK, so I also keep a to-do list, and will write down things I’ve done just to cross them off…