Here's how to not do a Changes file:
That tells me nothing about whether I want to upgrade my SpamAssassin install. :-(
Oh, look, I wrote about this before, and how great Tim Bunce's Changes files are.
The fourth Italian Perl Workshop will be September 18th and 19th in Pisa. Organizers are calling for talks, but haven't yet set up the website.
From David Fetter's page at http://fetter.org/optimization.html:
- The first rule of Optimization Club is, you do not Optimize.
- The second rule of Optimization Club is, you do not Optimize without measuring.
- If your app is running faster than the underlying transport protocol, the optimization is over.
- One factor at a time.
- No marketroids, no marketroid schedules.
- Testing will go on as long as it has to.
- If this is your first night at Optimization Club, you have to write a test case.
Of course it's company policy never to imply ownership of a performance problem. Always use the indefinite article: "a performance problem", never "your performance problem."
Jan Dubois posted about Microsoft's 3rd Annual Scripting Games, where you can win prizes for writing Perl programs to solve programming problems like "find a word that you can make out of a phone number," and "count the number of characters in a given text file."
I'd enter if there were interesting prizes, but all the prizes for Windows-only software packages. :-(