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.

Information/thoughts about The Pattern Handbook by Linda Rising

(I havn't commented all articles in the book, yet)

Patterns: Spreading the Word by Linda Rising
Page 31
How patterns were introduced at AGCS. They had brown-bag meetings for the interested, made sure that all intrerested designers got their own copy of the GoF-book. Patterns are best learned when you try to apply it into your own projects, so it's best to have time for consulting when you have a pattern-course.
Writer workshops is a good way to develop patterns.

A Training Experience with Patterns by Brandon Goldfedder & Linda Rising
Page 37

Pattern Writing by Linda Rising
Page 69
Mostly about the different forms in which a pattern can be written.

Improving Software Development at AG Communication System by Norm Janoff
Page 121
Experience with Process & Organizational patterns.

HandsInView by Don Olson
Page 139
A real life pattern about skiing.

A Pocket-Sized Broker by Don Olson
Page 171

Setting the Stage by James O. Coplien
Page 301
A column by James Coplien, about what patterns are and their origin, followed by a description of Counted Body Pattern.

Software Design Patterns: Common Questions and Answers by James O. Coplien
Page 311
available on the web at: http://axaonl.cern.ch:8000/a_doc%24www/ONLINE/oo-patterns-questions_and_answers.ps

The Failure of Pattern Languages by Richard P. Gabriel
Page 333
Some notes on why pattern languages might not work. Interesting that Alexander himself came to the conclusion that it didn't work after others tried out his pattern language and made poor results. This article is a summary of Alexanders thoughts after applying his ideas to develop houses.
Perhaps one should read Alexanders later work as well, since he came to many conclusions after "Timeless" and "Pattern Language"?

Potential Pattern Pitfalls, or How to Jump on the Patterns Bandwagon Without the Wheels Coming Off by Neil B. Harrison
Page 345
A good article on the downfalls of patterns, and the cure for them.

An Introduction to Patterns by Ralph E. Johnson
Page 353
An introduction that describes the pros/cons when using the Composite pattern [GoF].

Patterns and Frameworks by Ralph E. Johnson
Page 375
What the difference between a framework and a pattern is. Which patterns the framwork MVC (Model/View/Controller) consists of, mainly Observer, Composite and Strategy, and their roles in the MVC. Pros/cons for framworks vs patterns.

Patterns and Antipatterns by Andrew Koenig
Page 383
The first thoughts about creating antipatterns, that they coins down solutions that appears to work, but will bring problems with them.

Pattern Hatching - Perspectives from the "Gang of Four" by John Vlissides
Page 505
More of a introduction to Design Patterns. It tells why GoF choose to their form for their Design Patterns, and it gives an example of the Composite pattern [GoF].

Appendix A: Annotated Bibliography
This are employees at AGCS's thoughts on many pattern-books.

[GoF] Design Patterns : Elements of Reusable Object-Oriented Software, known as the GoF-book (by the "Gang of Four")

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