Software Engineering, Project Management, and Effectiveness
The beauty of patterns is that the insight is timeless. I was flipping back through a post on Architecture, Mobiles, and Health: 10 Pitfalls, by Eduardo Jezierski. Ed is a friend and we worked together for years, first in Microsoft Developer Support, and then in Microsoft patterns & practices. When Ed shares what's on his mind, he has an uncanny ability to put into word things that you have bumped into or know to be true, or a new lens that you need to look through.
This post is a roundup where I cherry pick my favorite points from his post on his lessons learned. Many of the points especially resonate because we they ecapsulate and magnify points we learned over time in patterns & practices, as we focused on architecture, viewpoints, scenarios, context, principles, patterns, and antipatterns.
Key Take Aways on Architectural Approach Here are my key take aways from Ed’s learnings on software architectural approaches:
Key Take Aways on Architectural Antipatterns Antipatterns are what not to do, or in the words of Jim Coplien -- "an anti-pattern is something that looks like a good idea, but which backfires badly when applied." Here are my key take aways from Ed’s learnings on antipatterns:
These are just my notes and take aways from Ed’s illuminating post. Ed’s actual post is rich with elaboration and examples, and it connects the dots. Check out Architecture, Mobiles, and Health: 10 Pitfalls.
I think I'd need to say that a lot of this I got sensitized to from yourself and the p&p team. Keep bringing out the proven-practice, context-sensitive guidance to help your customers succeed!