PED advocates one principle
for inspiring software engineers.

1.  Pattern First Thinking

In the beginning, when writing your first line of test code, keep in mind simple (single) class patterns. Attentive pattern selection can expedite the journey to loosely-coupled high-cohesion applications.

Pattern First Thinking

Principles 2 through 4 are relevant
for empowering project teams.

2.  Pattern Palette Adoption

Upon project inception, move quickly to adopt a coherent Pattern Palette. Continue to mature your team palette throughout the project life cycle.

Pattern Palette Adoption

3.  Global Understandability

When authoring a business narrative in Java, imagine the potential reading audience. Such a narrative—your code—may be durable for decades.

Global Understandability

4.  JUnit Strategy for Testing 

Pursue convenient JUnit testability. Encourage frequent invocation of IDE test coverage using functionally equivalent services.

JUnit Strategy for Testing


Principles 5 through 8 are relevant
for harmonizing enterprise communication.

5.  Unified Pattern Language

An enterprise pattern language can offer your project team an accelerated starting point for adopting their own Pattern Palette.

Unified Pattern Language

6.  Adaptable Technology Wrapper

Aligning an API with a Unified Pattern Language gives rise to source consistency. A wrapper approach supports underlying technology choice.

Adaptable Technology Wrapper

7.  Reference Application

When seeking application architecture, design, or implementation recommendations, use a reference application as an alternative to comprehensive documentation.

Reference Application

8.  Instructor Guided Training

When learning a reference application consider face-to-face, hands-on, training. Instructor elaboration provides additional context for self-study.

Instructor Guided Training