News for hackers. Stuff that matters.
Re:We promoted developers into architects without informing ... by alphazard on Friday November 20, 2026 @03:41PM (#50581734)
> Am I an outlier in that every SWE job I've had has expected you to push back on requirements and design the data model for tickets you are handed?

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.

Re:We promoted developers into architects without informing ... by monocasa on Friday November 20, 2026 @04:02PM (#50582050)
I've always treated the architect role as more setting broad goals, defining boundaries for individual ownership, and technical dispute resolution. Sort of what you see with a lot of directors of movies where you get the best work by empowering individuals to completely own a carefully built little box that is a brick in the larger work.

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.

Re:We promoted developers into architects without informing ... by benji8000 on Friday November 20, 2026 @05:13PM (#50583056)
> architect always ends up knowing less about the system

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.

Re:We promoted developers into architects without informing ... by spiralpolitik on Friday November 20, 2026 @05:18PM (#50583124)
Good architects delegate down and are there to ensure the big picture remains consistent while leaving the teams to sweat the details because they are closer to the problem.

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.

Re:We promoted developers into architects without informing ... by suzzer99 on Friday November 20, 2026 @06:31PM (#50583875)
Bad architects insist you add things like websockets because they already put it in the Powerpoint, even though app has zero need for them.
Re:We promoted developers into architects without informing ... by cebert on Friday November 20, 2026 @06:40PM (#50583956)
I really hope AI eliminates enterprise architect roles. It is uninspiring to get direction from people who don’t do anything or build anything.
Re:We promoted developers into architects without informing ... by theK on Friday November 20, 2026 @06:58PM (#50584147)
I think it won't. At least I don't see how.

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.

Re:We promoted developers into architects without informing ... by lokar on Friday November 20, 2026 @07:00PM (#50584162)
When in that role I focus on supporting the team. Mentoring, resolving disagreements, providing broader context, suggesting more options to consider (often stuff we could copy from older systems), etc.

The main area where I spend influence on really shape the outcome is on process and team culture, not any specific technical decision.

Re:We promoted developers into architects without informing ... by wreath on Saturday November 21, 2026 @12:54AM (#50586388)
Thats a technical lead,no?
Re:We promoted developers into architects without informing ... by jeremyjh on Friday November 20, 2026 @06:07PM (#50583657)
A lot of organizations don't know how to hire and task architects appropriately. I had the same opinion until I worked in an org where they actually functioned the way you'd think they should. Then I saw the chief architect's name in a 20 year old commit. They had no idea how to hire new ones, but they'd figured out how to grow and task them, which is a good substitute.
Re:We promoted developers into architects without informing ... by theK on Friday November 20, 2026 @06:49PM (#50584050)
> Architects are a bad meme, along the same lines as scrum masters and product managers

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.

Re:We promoted developers into architects without informing ... by sjpb on Friday November 20, 2026 @06:54PM (#50584104)
[delayed]
Re:We promoted developers into architects without informing ... by theK on Friday November 20, 2026 @07:03PM (#50584193)
My notion here is that Taylorism's defining principle is the separation of conception (planning, design) from execution (doing).
Re:We promoted developers into architects without informing ... by antonvs on Friday November 20, 2026 @11:10PM (#50585851)
> 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.

Re:We promoted developers into architects without informing ... by mschuster91 on Friday November 20, 2026 @08:04PM (#50584684)
> 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.

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...)

Re:We promoted developers into architects without informing ... by andrekandre on Friday November 20, 2026 @09:02PM (#50585122)

  > 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!
Re:We promoted developers into architects without informing ... by mepiethree on Friday November 20, 2026 @10:33PM (#50585646)
I’m sorry you’ve clearly never worked with a decent product manager
Re:We promoted developers into architects without informing ... by timr on Friday November 20, 2026 @11:08PM (#50585841)
> Architects are a bad meme, along the same lines as scrum masters and product managers

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.

Re:We promoted developers into architects without informing ... by jameshart on Friday November 20, 2026 @11:37PM (#50585991)
All software development is architecture. Decide to implement a change by adding an if block to some code, by adding a function, by creating a new module and implementing it there, locally in the browser or on the server… those are all architectural decisions.

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.