Programmers or businesscritters?

Good programmers don’t usually make good business leaders. Programmers are typically introverted, have awkward social skills, and often aren’t very good about paying their own bills, much less fighting to close deals and get customers to pay up. This ability to be so good at one thing and so bad at another stems mainly, I think, from the fact that programming is an individual sport, where the best work is done, more often than not, just to prove that it can be done rather than to meet any corporate goal.

From Accidental Empires, chapter 6.

Depending on what you value in life, it's important to make sure that you're aiming at the right goal.

Cleaning up your CPAN directory

The Perl Monks speak

You can always delete .cpan/build and .cpan/sources, which is where the bulk lives.

I have been wondering this for weeks! Good thing I remembered about Google existing and searched for the answer.

Some wisdom about multithreading

If you've spent years learning tricks to make your MT code work at all, let alone rapidly, with locks and semaphores and critical sections, you will be disgusted when you realize it was all for nothing. If there's one lesson we've learned from 30+ years of concurrent programming it is: just don't share state. It's like two drunkards trying to share a beer. It doesn't matter if they're good buddies. Sooner or later they're going to get into a fight. And the more drunkards you add to the table, the more they fight each other over the beer. The tragic majority of MT applications look like drunken bar fights.

From the ØMQ guide. It looks like a fine product, and I hope to become a pro with it soon.