As an architect, you have been picked from your organization's top technical talent. Your architecture is intended to guide and constrain. But not imposing your best ideas and lessons learned on designers and developers.
By trying to wield too much power and you will encounter resistance. Wield too little, and you make no contribution. The solution is to take a minimalist approach to architecture—sort out what your highest priority architectural requirements are, and then do the least you possibly can to achieve them! That is, you should keep your architecture decision set as small as possible, while ensuring that your key system priorities are met.
No comments:
Post a Comment