PED advocates one principle for inspiring software engineers.
In the beginning, when writing your first line of test code, keep in mind a simple class pattern. In the end, your software will be more flexible.
Principles 2 through 4 are relevant for empowering project teams.
Starting with project inception, adopt a coherent Pattern Palette by beginning with a proven pattern language. Continue to mature your team palette throughout the project life cycle.
When authoring a narrative in Java, imagine the potential reading audience. Such a narrative—your code—will be understood beyond a pair programmer and immediate project team.
Ensure pattern implementations are conveniently testable to encourage frequent running of the complete test suite using functionally equivalent services.
Principles 5 through 8 are relevant for harmonizing enterprise communication.
When promoting a shared Pattern Language organize patterns into collections. The project teams throughout the enterprise will have a starting point for adopting their own Pattern Palette.
When aligning an API with a Pattern Language consider using adaptable technology wrappers as a way to increase programming consistency regardless of technology choices.
When promoting application architecture, design or implementation recommendations, establish a reference application as an alternative to comprehensive documentation.
When introducing a reference application into the enterprise, consider offering hands-on face-to-face instructor guided training so that participants become comfortable using the reference application as a self-study resource.