Contribution 43

From WikiContent

Revision as of 05:07, 8 June 2008 by BarryHawkins (Talk | contribs)
(diff) ←Older revision | Current revision (diff) | Newer revision→ (diff)
Jump to: navigation, search

Value stewardship over showmanship

When an architect enters a project, there is an understandable desire to prove one's worth. Being assigned the role of software architect typically indicates implicit trust on the part of the company in one's technical leadership, and it only follows that one would desire to make good on that expectation as soon as possible. Unfortunately, there are those who labor under the misapprehension that proving one's worth consists of bedazzling if not baffling the team with one's technical brilliance.

Software architecture is about serving the needs of one's customers, typically through direction from those with domain expertise that surpasses one's own. Pursuing successful software development will lead one to create solutions of compromise, balancing the cost and complexity of implementation against the time and effort available to a project. That time and effort are the resources of the company, which the software architect must steward without self-serving undercurrents. Unduly complex systems that sport the latest hot framework or technology buzzword seldom do so without some sacrifice at the company's expense. Much like an investment broker, the architect is being allowed to play with their client's money, based on the premise that their activity will yield an acceptable return on investment.

Value stewardship over showmanship; never forget that you are playing with other peoples' money.

By Barry Hawkins

This work is licensed under a Creative Commons Attribution 3

Back to 97 Things Every Software Architect Should Know home page

Personal tools