This Article 
 Bibliographic References 
 Add to: 
Code Matters!
March-April 2012 (vol. 29 no. 2)
pp. 81-83
Frank Buschmann, Siemens Corporate Technology
Jörg Bartholdt, Siemens Corporate Technology
There is broad consensus that architects should code. Yet the challenging question is: how can architects program without being lost in myriads of local code details? Even when they program they should be in full control of a system's entire architecture. Thus, architects should not program for fun or to be accepted by developers. Instead they should program to guide an architecture's realization and get feedback on the sustainability and habitability of their own designs! Agile practices help architects to balance their coding activities with other duties, allowing them to be in control of the amount of time they spend on programming and the concerns and system parts on which they program.

1. S. Brown, "Software Architecture for Developers," Coding the Architecture, online book;
2. B. Vande Ghinste, "Do Architects Need To Code?" blog; 2010/05/07do-architects-need-to-code.aspx .
3. J.O. Coplien and N. Harrison, Organizational Patterns of Agile Software Development, Prentice-Hall, 2004.
4. K. Beck, eXtreme Programming Explained: Embrace Change, Addison-Wesley, 2004
5. F. Buschmann, "Tests: The Architect's Best Friend," IEEE Software, vol. 28, no. 3, 2011, pp. 7–9.

Index Terms:
coding architect, agile programming practice, test driven development
Frank Buschmann, Jörg Bartholdt, "Code Matters!," IEEE Software, vol. 29, no. 2, pp. 81-83, March-April 2012, doi:10.1109/MS.2012.27
Usage of this product signifies your acceptance of the Terms of Use.