Pair with an Architect

From Programmer 97-things

Jump to: navigation, search

Architects and developers often have a need/hate relationship. Each needs the other to be able to get things done. But often at least one doesn’t respect the other. This is a shame because both could gain a lot of personal benefit from a better relationship. Developers need to stay current on the latest technologies. They are constantly learning more and more details about how to apply a few technologies. Architects have trouble diving into the details of any one technology because they must understand so many different technologies and how they fit together. Developers can help architects stay current by inviting them to pair when working on key problems.

Architects often choose the technologies to be used in projects. The poor developer is left to sort out the details when it comes time to implement the functionality. This can be a lot harder than expected by the architect. Developers benefit when the architects have more hands-on experience with the technology as a result of pairing with developers. Architects are often seasoned technologists themselves with a wealth of experience. Developers can tap into this experience by asking the architects to pair with them. The architect will often point out ways to reorganize the code to make more robust or reusable. The developer is likely to learn how to use abstraction and encapsulation more effectively.

Personal tools