Ground Truth Document

Not a spec, but a statement. Positive, not normative. I like it. Can't get to where you want to go unless you know where you are.

The practice that goes with this term is simple: always put your ground-truth document together before you start on production code (test tools to reverse-engineer the device are not production code). Maintain it with the code, treat it as the authority for how the code should behave, and when the code doesn’t behave that way treat the divergence as a bug. When your knowledge about how the device behaves changes, change the code second; change the ground-truth document first. (Of course you have it under version control, so you also have a history of your knowledge of the device.)

Indirect object notation going byebye in Perl 7

Long awaited and I hate it but still bittersweet somehow - the old way of doing things reminds me of a simpler time, when code was code and filehandles were . . . I still don't really understand what filehandles are.