PED advocates one principle for inspiring software engineers.
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.
Principles 2 through 4 are relevant for empowering project teams.
Upon project inception, move quickly to adopt a coherent Pattern Palette. Continue to mature your team palette throughout the project life cycle.
When authoring a business narrative in Java, imagine the potential reading audience. Such a narrative—your code—may be durable for decades.
Pursue convenient JUnit testability. Encourage frequent invocation of IDE test coverage using functionally equivalent services.
Principles 5 through 8 are relevant for harmonizing enterprise communication.
An enterprise pattern language can offer your project team an accelerated starting point for adopting their own Pattern Palette.
Aligning an API with a Unified Pattern Language gives rise to source consistency. A wrapper approach supports underlying technology choice.
When seeking application architecture, design, or implementation recommendations, use a reference application as an alternative to comprehensive documentation.
When learning a reference application consider face-to-face, hands-on, training. Instructor elaboration provides additional context for self-study.