Try before choosing
[early draft of the concept; compete, observe, choose]
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.
This work is licensed under a Creative Commons Attribution 3
Back to 97 Things Every Software Architect Should Know home page