3 ms·

> Have a few, select people approve this plan before starting work. How are these ppl selected. This contradicts org structures where "architects" are suppose

> Have a few, select people approve this plan before starting work. How are these ppl selected. This contradicts org structures where "architects" are supposed to give "guidance" and enforce a "uniform vision".

closeparen 8y ago
We have something like this at work. Approvers are generally respected senior engineers adjacent to the author and representatives from consumers/dependencies of the new system.
qznc 8y ago
Your use of quotes suggests some grudge against architects. I am an architect and I consider my role as one to give guidance and enforce a uniform vision (although "enforce" sounds like I would actually have significant power over this chaos here). For example, last week I learned about situation which caused frustration to our developer for months already. After a few hours I confidently could give them guidance what they should do in the short-term, what will happen long-term and how we should handle it. I agree that architects sometimes solve too general problems instead of addressing the immediate problem. I'm guilty of this myself. An architect has the responsibility to think further and wider than a developer while also being able to consider the details. I sometimes switch to the wrong gear. Back to the actual topic: The relevant architect is just one of the select people to approve the plan. I would love it if I would hear about new plans in written form. Unfortunately, it is usually in some meeting. This modus operandi forces me to sit in lots of meetings which are rarely relevant to me. Even worse, sometimes it is only through rumors which means lots of followup emails to clarify. We actually do have a similar process to the one in the article, but without step 4 "Send this planning document out to all engineers". I suggested something like this a few times but most people complain that they get too much mail anyways. I also did mail to everybody a few times and it was helpful. So I fully agree with the article, but I lack to power to implement step 5 "Have everyone follow the above steps" so far.

closeparen 8y ago

We have something like this at work. Approvers are generally respected senior engineers adjacent to the author and representatives from consumers/dependencies of the new system.

qznc 8y ago

Your use of quotes suggests some grudge against architects. I am an architect and I consider my role as one to give guidance and enforce a uniform vision (although "enforce" sounds like I would actually have significant power over this chaos here). For example, last week I learned about situation which caused frustration to our developer for months already. After a few hours I confidently could give them guidance what they should do in the short-term, what will happen long-term and how we should handle it. I agree that architects sometimes solve too general problems instead of addressing the immediate problem. I'm guilty of this myself. An architect has the responsibility to think further and wider than a developer while also being able to consider the details. I sometimes switch to the wrong gear. Back to the actual topic: The relevant architect is just one of the select people to approve the plan. I would love it if I would hear about new plans in written form. Unfortunately, it is usually in some meeting. This modus operandi forces me to sit in lots of meetings which are rarely relevant to me. Even worse, sometimes it is only through rumors which means lots of followup emails to clarify. We actually do have a similar process to the one in the article, but without step 4 "Send this planning document out to all engineers". I suggested something like this a few times but most people complain that they get too much mail anyways. I also did mail to everybody a few times and it was helpful. So I fully agree with the article, but I lack to power to implement step 5 "Have everyone follow the above steps" so far.