Keep your architect busy
From Programmer 97-things
Architect is probably the most prestiguous technical job available in software development. They are to be technical experts with skills and knowledge well beyond technology, and your project shall be lucky to have one of these available.
Having said that, very likely it is not easy to deal with the architect of your project. He may appear arrogant, or too busy, or occupied with some vague project to be started sometime in the future. This stance is so common that most sources of advice for architects also care for the attitude and working habits. However, there is the other side of the coin. You must not let him out of duty. And there are important duties where an architect could really help you.
First of all, problems need to be solved at any time during a project. It is a myth that the "architectural" issues are treated at the start of a project. In fact during implementation you come to learn about many things that turn out to be relevant for the overall project success. Some may need more clarification than initially expected, others outrightly contradict what an architect had stated months ago. Keep him in charge.
Secondly, your architect probably knew about the art of deciding no earlier than necessary. If you manage to delay decisions to the point in time where they are actually needed, you gain more opportunities for your project - a larger option space you can navigate in. Plus, the decisions will be better informed. If you come to such a point where a decision is needed, however late in the project: it is the architect to make it, at least know about it.
Thirdly, someone who does the decomposition of a system should also be held responsible for its re-composition. This means that the architect who structured the system, should also be the key integrator who takes care that the developed pieces fit together and can be made work. Such a reciprocal definition of responsibilities will let every architect be more careful and a bit humble - leaving little room for arrogance. An architecture may even put its main focus on the final integration, leading to an IntegrationDrivenArchitecture.
Last not least, if you keep your architect busy every contact with him is a learning opportunity for you. This will widen your horizon and give you career options, it helps the project and keeps architectural knowhow available, and it provides feedback to the architect about his work. Your personal win is not the least in this setting.
This work is licensed under a Creative Commons Attribution 3
Back to 97 Things Every Programmer Should Know home page
