Contribution 33

From WikiContent

(Difference between revisions)
Jump to: navigation, search
m
m
Line 1: Line 1:
 +
== Try before choosing ==
 +
[early draft of the concept]
[early draft of the concept]
Line 4: Line 6:
Our new and modern architect, when he has a suitably large team, asks a few team member to solve the problem, then let's them work with it for a while, and finally gets everyone together and pick the best solution.
Our new and modern architect, when he has a suitably large team, asks a few team member to solve the problem, then let's them work with it for a while, and finally gets everyone together and pick the best solution.
 +
 +
 +
By [[Erik Doernenburg]]
 +
 +
This work is licensed under a
 +
[http://creativecommons.org/licenses/by/3.0/us/ Creative Commons Attribution 3]
 +
 +
 +
 +
Back to [[97 Things Every Software Architect Should Know]] home page

Revision as of 05:29, 26 May 2008

Try before choosing

[early draft of the concept]

Let's assume we delay important technical to the last responsible moment [is this maybe another point for this list?], how do you make the decision? A stereotypical architect might gather all the information, then mull over it for a while, and finally decree the solution from the ivory tower.

Our new and modern architect, when he has a suitably large team, asks a few team member to solve the problem, then let's them work with it for a while, and finally gets everyone together and pick the best solution.


By Erik Doernenburg

This work is licensed under a Creative Commons Attribution 3


Back to 97 Things Every Software Architect Should Know home page

Personal tools