4 ms·
Yes but the reality of decisions is that one person needs to drive that decision - a group of people will often struggle to make a clear decision every time
by br3w5 12y ago
Yes but the reality of decisions is that one person needs to drive that decision - a group of people will often struggle to make a clear decision every time
- crdoconnor 12y agoAgreed, but that person doing the driving is often different from one discussion to the next. And it's better that way - especially when people speak up about issues that they personally feel invested in or passionate about. This has been my experience, anyway.
- arethuza 12y agoI've had "architect" in my job title for ~15 years and I'm very clear that my job is not to make the key technical decisions, but to facilitate the process for making these decisions.
- meekins 12y agoAgreed. An architect should be a knowledgeable generalist able to facilitate the discussion. Personally I'd hate to be the "smartest guy" in the team about anything. However I spend a large part of my work days collaborating with all different stakeholders and different subsystem vendors and what I as an architect bring to the table is the requirements based on the context of the subsystem we work on. Rest of my days I design, code and debug just like the rest of the team.