Most of the time, when guys were explaining the role of the software architect to me, I was not able to believe it would be possible to organise software development on such a division of responsibilities. I always feel the architecture is a discipline each member of a team should embrace. The " Design Patterns Quick Reference " from Mc Donaland is really useful because it allows the team to speak about the most appropriate choice in front of this great summary. But a common pitfall with these pattern design concepts is the fact people will over design and move to a solution too complex. One solution resides in the Test driven development principles where after coding the test and writing the code for them to pass, there is the refactoring step. This is the good moment to consider inserting a design pattern. Make things work, then focus on building maintainable code. Sources : Mcdonaldland : mcdonaldland » Design Patterns Quick Reference Davidhayden : Design Patterns and Agil...
A place to share my questions, my journey in digital knowledge, product management, and climate action.