...and when I'm on good behavior, that means a fairly extensive pod, with caveats, gotchas, and usage examples, if the script has more than a very few options. (Sometimes I have the feeling that many script writers carry over their key-stroke saving practices, as used within a script, to the documentation, where such terseness can be a significant obstacle for the "future user.")
- a useage sub or block called when required arguments are not present or when user adds (any of) ?help, /h, /help, etc
- in line comments on any code I find "tricky"
...for which the maintenance programmer's or future user's mileage may vary
The last is sometimes disparaged, as "inelegant" or even "inept" but like your Cobol options, IMO such comments are worth enough (even for the current writer, 6 months later) to discount the disfavor they earn with some people, as not all prospective maintainers/users will know the meanings as you do.