Those could be done by normal management, but I've found it better to separate those discussions from management style discussions. Sort of like how the BDFL role in a large open source project is rarely anyone's actual boss.
Albeit, I'm still recalibrating what all this means in an agentic world. It makes sense with the little swarm I directly command, but the pressures for downstream ICs to ignore the art and taste of what they're doing is more than a bit unfortunate since the core of what I'm saying is to empower them to give a shit and be proud about what they built.
I guess that depends. In automotive, at least in my case, the SW architect on our team knows so much more about how our SW module interacts with the overall system, it's almost awe-inspiring. My guess is, they have all this knowledge because they're continuously interacting with other architects and teams to talk about the big picture.
Bad architects try to micromanage and those are the cases where you end up with systems that are slow and unworkable with processes that have too much ceremony.
AI still doesn't really teach anything on the org-dev level. Organizations that where dysfunctional in the past will keep growing these structures only that now the complexity will increase much much faster because teams can do (vibecode) so much more.
The main area where I spend influence on really shape the outcome is on process and team culture, not any specific technical decision.
I think it says a lot about our culture that, even though xore agile literature and practices like XP and DX have again and again shown what works, the IT world stubornly keeps gravitating towards taylorian structures.
A big reason is that they're always trying to hire the cheapest possible developers, with corresponding skill levels, so a big part of the architect's task becomes to try to impose some sanity on the collection of issues that result.
A good architect is IMHO someone who can get the bullshit out of your way. Think like interfaces with third parties (or even other departments at your average megacorp), it certainly doesn't hurt if someone else has both the awareness and the technical knowledge about dependencies I have or others have on me, and can take care of dealing with the associated bureaucracy.
(And no, that's not a PM role because most PMs can't tell JSON apart from XML...)
> Architects are a bad meme, along the same lines as scrum masters and product managers. Good software engineers spend more time on design than implementation, and the best are helping their teammates
preach brotha!Whoa there. Bias detected.
Look...I know firsthand that a lot of PMs are useless, political, bureaucratic spreadsheet jockeys, but good ones are immensely valuable.
Just like programmers who don't know how to design a data model, or "scrum masters" [1], PMs who know nothing about code or the domain are either heading rapdily for extinction, or are going to evolve into a population of hyper-political ringwraiths whose only job is to suck up to management [2].
[1] OK, I can't bring myself to say anything good about this position. Maybe I have bias too.
[2] Hopefully the former. Fingers crossed.
Large scale software development is just a nested series of architectural choices from top to bottom.
That some organizations choose to give some software developers the job title of architect is not a ‘bad meme’, it’s a reaction to the realization that there’s a lot of architectural decisions being made and it might be nice if all the people making them had sufficient information to make them right.
Good ‘architects’ focus on making sure developers who are making all those architectural decisions have the right context to make them.
Bad ‘architects’ try to make - or preempt, or second guess - all those decisions that have to be made. That doesn’t scale and doesn’t work.
Yes, that is how most functional organizations operate.
Architects are a bad meme, along the same lines as scrum masters and product managers. Good software engineers spend more time on design than implementation, and the best are helping their teammates with design, and auditing designs of adjacent teams to ensure integration success. So architecture is an important part of the job, but that doesn't mean that you can automatically declare a role with the title "architect" and make the whole organization do better design.
Architect roles are a bad meme because the architect always ends up knowing less about the system and how it is used than the engineers and support staff, yet they have more influence over the decisions affecting those things. That's the essence of an organizational anti-pattern/bad-meme any time it shows up: influence over resources anti-correlated with decision quality. Additionally, architects often report to non-technical folks fairly high up the chain. Those people are bad at screening for such a technical role, sometimes even making the mistake of replacing an architect with an external hire.