These pages about different languages / apis / best practices were mostly jotted down quckily and rarely corrected afterwards.
The languages / apis / best practices may have changed over time (e.g. the facebook api being a prime example), so what was documented as a good way to do something at the time might be outdated when you read it (some pages here are over 15 years old).
Just as a reminder.

About Pattern Languages of Program Design 2

Pattern Languages of Program Design 2

This book at Amazon.co.uk

My plan is to add some comments about the patterns in the book as I read it, but to be honest I am quite convinced that I won't have the time, but nevertheless, here's a try, starting with a pattern for the WWW:

Pattern no.26 page 417
How to organize an Essay-based Web site by Robert Orenstein

Provides guidelines for good ways to organize a web site, how to link between documents etc.
The pattern is from 1995 and naturally the web has changed quite a lot, but many of these guidelines applies since they mostly involve how to present text-documents. For example one tip that is useful is to have an unique image at the top of each document that visually summarize the document.

More programming related pages

Workflow: Release process
Workflow: Bug tracking
Teambox (Redbooth) - Mantis connector
Design Patterns
Git & Github
Go / Golang
CVS backup script
Distribution process
Installation script
Java Server Faces
Perl tips
Perl links
Python / py2app
Shell scripts
Facebook / Opengraph
PHP developer notes
Redbooth API through php
Website optimization
jqTableKit demo
Javascript / html / css links