Serg

“Many software projects get software architects involved only in the design phase, then they move to other projects or the consultation contract ends. How can they ensure that their deliberate architectural decisions have been implemented correctly? Their decisions will be at best good intentions unless they follow-through with them.”
― Richard Monson-Haefel, 97 Things Every Software Architect Should Know

“Most projects are built by people, and those people are the foundation for success and failure. So, it pays to think about what it takes to help make those people successful.”
― Richard Monson-Haefel, 97 Things Every Software Architect Should Know

“As you work in requirements meetings to design software, pretend that your customer is not your customer. It turns out that this is a very easy thing to do, because it is true. Your customer is not your customer. Your customer‘s customer is your customer. If your customer's customer wins, your customer wins. Which means you win.”
― Richard Monson-Haefel, 97 Things Every Software Architect Should Know

“Design is a discovery process, as we implement we discover new information, often impossible to know up front. By accepting that design is an ongoing and empirical process in a forever changing world, we learn that the design process must be flexible and ongoing too. Clinging onto your original designs and trying to force them through is only going to end up with one result so you need to learn to understand that it will never look like that.”
― Richard Monson-Haefel, 97 Things Every Software Architect Should Know