Structure in the flow

As a theme of this blog is information overload, I need to point this out: an email charter, a set of principles for senders to respect to make email overload less of a problem. Here’s a blog post on its elaboration.

The fact is, a lot of information overload could be dealt with at the source, if the sender/publisher had more care for the time of the recipient/audience. Conventions such as these, or as netiquette, need to be made explicit to get more adoption.

I’ve also made two small updates to pages:

• On the page about monitoring pages for changes, I now recommend using Firefox SiteDelta (or other locally installed software) as Google web page monitoring feature has been cancelled
• For code snippet organization, I now point to this discussion at StackOverflow which is a nice overview of the wide range of options people use