Pattern-Oriented Software Architecture For Dummies

Write Your Own Patterns

When you start writing your own patterns, think about what you're an expert in. To narrow down the area(s) in which you're an expert, keep some notes about the specific questions that people ask you over and over, such as the following:

• How do I get the compiler to work?
• How do I set up the IDE?
• How do I use the XYZ protocol?

If there isn't already a pattern that explains how you answer the questions — write your first pattern as a solution to one of those questions.

Patterns are proven solutions. If you don't know the solution to the problem, you don't have a pattern.

Think about your intended audience. Who do you want to read your pattern and benefit from it? If you're writing about the things that people ask you about, your audience is probably your co-workers or friends. Write the pattern to answer their questions.

When the pattern is completed, label it a candidate pattern, and have your colleagues read and review it (refer to Chapter 5). After a review or two, the pattern will be able to stand on its own, and people can use it instead of asking you the same questions over and over.

Your pattern may be immediately useful to your workgroup or circle of friends. If you want it to be more widely useful, you need to make it widely available. If you're ...