> I find this distinction harmful. Are we going back to the days where there were programmers who did the grunt work and architects who told them what to do? N

> I find this distinction harmful. Are we going back to the days where there were programmers who did the grunt work and architects who told them what to do? No I don't think so. Where in the article did the author said he is telling other people what to do? What he said is > proposed software architecture consulted it with key developers, and made sure everyone is onboard Being an architect, or staff engineer in modern term, means that the person will need to use his experience and expertise to help the team to find appropriate solutions, present to the team, list out pros and cons, let them pick, and drive the change with other stakeholders.