News for hackers. Stuff that matters.
Re:We promoted developers into architects without informing ... by whycombinetor on Friday November 20, 2026 @02:14PM (#50580253)
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? Even when the org was large to have an architect, they just were just a figurehead and designed the original system, and ongoing decisions were made by the dev who picks up the ticket.

From that perspective, engineers are still engineers, just without the hands-on-keyboard coding. If that's all your job was, hands-on-keyboard coding with no decision making, yeah you're cooked and need to reskill.

Re:We promoted developers into architects without informing ... by rsyring on Friday November 20, 2026 @02:20PM (#50580359)
I run a development firm so we've had all kinds of clients and interacted with various external dev teams over the last 20+ years.

You aren't an outlier exactly, but there are way more devs than you are probably aware who are just told what to build and then have to go build it. So they don't have or never developed the consulting, planning, and architecture skills and experience.

The more our clients tend towards wanting a process like that, and the less they treat us like valued expert software consultants that can help shape their solution for the better, the worse the outcomes usually are.

Re:We promoted developers into architects without informing ... by CSSer on Friday November 20, 2026 @02:36PM (#50580646)
I'm a self-taught woman who started work in agencies doing front-end work, then moving on to progressively more complex tasks, eventually becoming a lead and doing all of the things you mentioned. Your experience maps to mine 1:1. I've had a lot of imposter syndrome and challenges around this, and I had to go through a similar realization at some point in my career. It sort of sucks because I am just not good at being that kind of blinders-on developer. I also mention my sex/gender because I've had lots of borderline offensive assumptions made about me in certain situations related to what you've described.
Re:We promoted developers into architects without informing ... by hinkley on Friday November 20, 2026 @02:36PM (#50580647)
We call those body shops. Probably because sweatshop sounds overwrought if you know what those are actually like.
Re:We promoted developers into architects without informing ... by hinkley on Friday November 20, 2026 @02:32PM (#50580576)
I would say that I expect senior engineers to have autonomy, and autonomy means not doing strictly what you are told. So if you’re not being told exactly what to do, that means you have to figure it out for yourself.

And that’s why junior engineers are fucked at companies that can afford to send all their proprietary information to Anthropic. But since they are public now, they will violate that trust as soon as major shareholders learn to word it so that it sounds like a stranded asset that any responsible C Corp would be expected to rescue. And then everybody’s fucked.

Re:We promoted developers into architects without informing ... by boogieknite on Friday November 20, 2026 @02:53PM (#50580925)
counterintuitively, i push back less now that im worried about standing out as "in the way of progress" when management is telling me to push their client manager nephew's vibe code to main
Re:We promoted developers into architects without informing ... by jimbokun on Friday November 20, 2026 @02:55PM (#50580955)
I'm seeing the Architects who only ever handed off a design based off of requirements to the dev and never implemented anything is equally cooked, in a different way.

There's really no sense in handing off the design to a dev to implement, who just copy pastes it into Claude's prompt. The "Architect" now needs to be fully responsible for what goes into production, instead of being able to blame some poor dev who faithfully implemented a flawed architecture design.

AI is flattening architecture and development into a single role.

Re:We promoted developers into architects without informing ... by 0x445442 on Friday November 20, 2026 @03:05PM (#50581130)
We used to call that role a Software Engineer.
Re:We promoted developers into architects without informing ... by bluegatty on Friday November 20, 2026 @03:18PM (#50581377)
If the new Engineers are making architectural decisions without a guiding Principal then it's a new job.
Re:We promoted developers into architects without informing ... by Fourier864 on Friday November 20, 2026 @03:31PM (#50581570)
It took me several years to realize this wasn't the default. Once I was senior enough to start getting people under me, I would assign tickets like "Scientist Bob would like a better method to view missing data, work with him to develop that over the next 2 weeks", and assume that they, like me, would enjoy the flexibility and the ownership. I didn't care what they came up with; email notifications, enhancing the web tool we have, putting coverage data in our opensearch to query, etc.

After getting complaints, I started getting narrower and narrower in my ticket writing, until I realized many newer software engineers literally want tickets like "modify function x_y_z() in python_file.py so that it also returns..."

Re:We promoted developers into architects without informing ... by MaKey on Friday November 20, 2026 @03:42PM (#50581754)
I guess these software engineers aren't needed anymore now.
Re:We promoted developers into architects without informing ... by zabriel_goss on Friday November 20, 2026 @03:43PM (#50581771)
Curious if this is a culture issue or a volume issue.

In the distant past of a couple of years ago, I saw and gave tickets with higher ambiguity and opportunity for ownership and cross-team collaboration. There was breathing room to take that kind of time.

This year, however, as we're all aware, the expectation around speed is much higher. When more spinning plates are added, I want them to be more defined so they can be handled quickly. To be clear, though, I much prefer the former scenario.

Re:We promoted developers into architects without informing ... by rizzom5000 on Friday November 20, 2026 @04:53PM (#50582796)
It's cultural from what I've seen. Especially where development time is micromanaged, story points mean minutes and hours and estimates are put under a microscope. In short, low trust environments where managers have never developed software and probably have no idea what is going on i.e. situationally unaware management.
Re:We promoted developers into architects without informing ... by aerhardt on Friday November 20, 2026 @03:43PM (#50581774)
Well honestly, those people have reason to be worried...
Re:We promoted developers into architects without informing ... by rescbr on Friday November 20, 2026 @03:44PM (#50581783)
Yeah. There are some teams I work with that are exactly like that, and it pisses me off. If I need to write the ticket in such detail then it would be faster for me to write the code myself.

Now with AI coding, it pisses me off even more.

Re:We promoted developers into architects without informing ... by teiferer on Friday November 20, 2026 @05:30PM (#50583271)
In my experience, that is still a little shortsighted. If you actually end up giving up and "just do it yourself" then you can often end up spending lots time with a long tail of fallout this entails. Suddenly some tests failing, some other team unexpectedly getting disrupted by your change and having to follow up on that and dealing with them, some follow up requirements revealing themselves... It is all those things that you are only on the hook for once you actually do it that often makes it worthwhile to instead dump all your thoughts into the ticket and then let somebody else do the grunt work, LLM-assisted or not. And it should add some humbleness to the attitude you just expressed.
Re:We promoted developers into architects without informing ... by theamk on Saturday November 21, 2026 @01:29AM (#50586575)
[delayed]
Re:We promoted developers into architects without informing ... by dalmo3 on Friday November 20, 2026 @04:57PM (#50582858)
> work with him to develop

Woah, no designer, no BA, no PO, no SME, no legal? I'm envious.

Aside, I've been thinking of the "reverse Uncle Ben": With great responsibility comes great power. Or should come. I've seen places where ICs were expected to "own" the work, as you mentioned, except they had no autonomy to actually make decisions, those would come by committee or from above. No wonder people didn't want the responsibility.

Re:We promoted developers into architects without informing ... by nomel on Friday November 20, 2026 @05:18PM (#50583119)
I've seen the opposite of that, too. In one position, I was told that results don't matter. It's the planning and process, presented through meetings, that everyone wants to see. Taking full responsibility, working with the actual people the work was for, directly, and delivering on time and with minimal issues during testing, giving them exactly what they wanted, with everyone actually involved happy, wasn't all that important.

Burned out from the misalignment of purpose of my work I couldn't stomach, then moved on.

Re:We promoted developers into architects without informing ... by weitendorf on Friday November 20, 2026 @05:03PM (#50582924)
I think this is definitely a very common experience. What makes it such a whiplash is that you're actually both at the beginning of a rather steep learning curve, but are only just becoming aware that the learning curve even exists / reluctant to consider the implications because of the impact it would have on your existing world model.

For inexperienced engineers it's that "your job is figuring shit out, not typing the code in", which for some people is like telling them that their dream job doesn't exist/the mental model most of their peers operate under isn't true.

For a manager it's that you can't really assume that everybody has the same personality/relationship to work/experience as you do, and that you might have even forgotten what it was like to be in their position, or not noticed how different some of your colleagues were from you. Which is also like telling them, "it turns out the best manager for your team is not the one you would want for yourself, and this job is going to be very different from what you thought".

I think it's very important to have a large enough sample of non-reporting colleagues across the range of experience. It helps you passively form a model of what normal career and even just life development looks like, and when you're in situations like this where you're not sure whether you're the asshole, or the other person is, or just confused, you can kind of in retrospect see how the near-peer may have navigated the same thing. Including business people. Our job is to add enough value to someone else's life that they're willing to pay us to stick around.

Re:We promoted developers into architects without informing ... by onthrowaway457 on Friday November 20, 2026 @05:17PM (#50583107)
Similar. As a PM I try to learn how much direction each person is cool with in this moment of the career. I don’t mind specific details if the person needs them, but I love it when the dev knows the domain, the problem space, etc and we talk about outcomes and capabilities then off they go, driving the momentum and making recommendations about scope reduction or additional features that I’d never have thought of in advance. Then I’m mostly breaking ties and figuring out the next important thing to build.
Re:We promoted developers into architects without informing ... by rootusrootus on Friday November 20, 2026 @08:13PM (#50584742)
Yes this has been a long time irritation for me. By the time I spec the feature to the degree these juniors require, I could have just done it myself. When I try to raise the level they work at, they just fall back to asking me incessant dumb clarification questions, refusing to take any ownership. No matter how often I have coached them on what the expectations is.

And now, I'm trying to get them to understand that if they persist in just being basic coders, they are shortly going to be replaced with an LLM.

Re:We promoted developers into architects without informing ... by socalgal2 on Friday November 20, 2026 @10:03PM (#50585489)
The problem for me is other people’s code. I don’t know what they want or what they will approve so I can’t just give them a solution that they’ll disapprove of. Having enough rejections leads to “tell me what you want me to type so that you’ll approve the pull request”
Re:We promoted developers into architects without informing ... by antonvs on Friday November 20, 2026 @11:11PM (#50585861)
> many newer software engineers literally want tickets like "modify function x_y_z() in python_file.py so that it also returns..."

...which makes them very replaceable by a coding agent.

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.

Re:We promoted developers into architects without informing ... by sanderjd on Friday November 20, 2026 @04:00PM (#50582010)
Yeah agreed, I have not experienced this as a change in my job expectations, I just have different (better) tools now. It would have been a change if this hit during my first or maybe second job, but not for a very long time now.
Re:We promoted developers into architects without informing ... by mshish on Friday November 20, 2026 @04:03PM (#50582076)
Agree, regardless of your engineering level, you need to own the security/performance within the scope of your change / ownership. Without that ownership, we're back to the old days where we ship things without caring about how they operate. I don't think that's where agentic coding tools are taking us.
Re:We promoted developers into architects without informing ... by jojogeo on Friday November 20, 2026 @04:20PM (#50582309)
The way I've always seen it in my mind; "hands on just doing coding" work is a Developer, and actually thinking about a problem and requirements etc, and composing a specification => code to solve a problem is Software Engineer.

Tbh I've always hated the developer role, they tend to be ticket bangers who don't give a shit about what they produce; as long as the sprint targets are achieved, (who gives a shit if a tonne of bugs come back in the next sprint(s) eh?).

Re:We promoted developers into architects without informing ... by Scarblac on Friday November 20, 2026 @04:56PM (#50582851)
I've been programmer, developer, software engineer, they were all exactly the same thing.
Re:We promoted developers into architects without informing ... by jojogeo on Friday November 20, 2026 @05:08PM (#50583003)
Depends on the org IMHO; I've always found that Developers appear in large quantities, usually hired from a "low cost economic zone", and are only interested in banging out code to achieve the stated goals in the JIRA tickets.

No independent thinking, no "Actually it would be better if we did X", they simply translate someone else's requirements into code which (allegedly) meets those requirements.

I agree though that the definition is vague, and orgs use the terms interchangeably. If you can't see the difference, then I'm sure that you're an excellent engineer and on the SWE end of the scale :)

Re:We promoted developers into architects without informing ... by Aurornis on Friday November 20, 2026 @04:23PM (#50582360)
> If that's all your job was, hands-on-keyboard coding with no decision making, yeah you're cooked and need to reskill.

I didn't understand this framing where a person is either a coder OR an architect, but not both, until I ran into a company that operated this way.

All of my jobs expected software developers to make and own their decisions, as well as ship at least some code related to the decisions they made.

The first time I encountered the coder-OR-architect separation was at a company that hired way too many people and held way too many meetings. They separated every responsibility out into different roles and then assigned those to different hires. There were so many roles that they couldn't even correctly identify the right boundaries between, for example, the Product Manager and the Product Designer, or the Project Manager and the Program Manager and the Engineering Manager.

The most surprising thing was how many people at that company liked it that way. The product managers liked writing up PRDs and then making them someone else's problems. The architects would translate those into big documents, then it was someone else's problem. The project managers would do elaborate ceremonies to turn them into tickets which became the coder's problem. The coders took the tickets and wrote enough code to close the ticket, then it became someone else's problem. Eventually the end product became the customer's problem.

I could see how comforting it was. You could settle into a constrained role and, as long you dutifully produced the artifacts of that role, it then left your plate and became someone else's problem. No one person held enough of the responsibility to be accountable for anything, because you could always point up and down the decision pipeline at someone else.

Re:We promoted developers into architects without informing ... by trentnix on Friday November 20, 2026 @04:23PM (#50582374)
At one of my previous gigs the CTO would, in one meeting, bemoan that none of the engineers were willing to make decisions and, in the next meeting, cut your knees out from under you for trying. Even today that same CTO is still in charge and his engineering team is still, for reasons mysterious to nobody who isn't in charge, unable to ship anything.

I'm very grateful that I'm now in a position where not only am I given as much rope as I'm willing to pull, it's expected of me.

Re:We promoted developers into architects without informing ... by sdevonoes on Friday November 20, 2026 @04:28PM (#50582428)
In 15 years of career, I have never seen or worked for a place that had only “coders” (people who were just typing code and not thinking or pushing back or giving their opinions about tech and product).

So whenever i hear that coders are out of job because of AI, I always wonder where were those “coders”. Never met one

Re:We promoted developers into architects without informing ... by switchbak on Friday November 20, 2026 @04:52PM (#50582783)
I've worked with folks who seem to identify as that being their job - but I don't think anyone ever wanted them to work that way.

Rigid roles are a reflection of a human desire to put people in tidy boxes, that doesn't mean those boxes map to reality in a useful way.

Re:We promoted developers into architects without informing ... by Pokepokalypse on Saturday November 21, 2026 @12:11AM (#50586149)
After you've worked at large companies (who tend towards defined roles: tidy boxes), and small start ups where - you do what needs being done; sometimes that even means a coder is doing demos to potential customers, or even investors.

It's a sharp contrast, and a weird contrast, and in the latter case, you're constantly challenged, constantly finding yourself outside your comfort zone, learning your limitations, what you like, what you dislike. I'm really really glad I didn't end up landing at a large company like I used to work (Symantec). Some people like that structure. I can't stand it.

Re:We promoted developers into architects without informing ... by onion2k on Friday November 20, 2026 @05:09PM (#50583010)
The belief is that prompting AI for some code gives you good architecture as well, because the AI magically knows what you aren't telling it. Or, maybe more generously, because a good vibe closer will give the AI a prompt that includes enough to derive what the architecture should look like.

If your use case is very ordinary it does work that way. It's only at the bleeding edge or in a weird edge case that performance or optimization stops being a problem you can solve by paying for a bigger box. The performance rarely matters for a SaaS CRUD app until you hit a scale where you've got a team of experienced devs, so most people vibing their next 'unicorn app' don't care.

Re:We promoted developers into architects without informing ... by spiralpolitik on Friday November 20, 2026 @06:29PM (#50583853)
The AI has been trained on what the statistical common practices are. In most cases these are the best practices. What the AI lacks is the ability to spot the cases where the best practices don't work or need tuning. That's where experience comes into play.
Re:We promoted developers into architects without informing ... by marssaxman on Friday November 20, 2026 @05:52PM (#50583496)
That was the role Microsoft seemed to expect of me, back in 2008-2009. Here's the spec, go type in the code, the suitability of the design is not your concern.

I did not like that very much, and did not stay too long.

Re:We promoted developers into architects without informing ... by steelframe on Friday November 20, 2026 @11:04PM (#50585822)
I was there during that same period of time. What you experienced was largely due to the PMs wresting control of the company from the engineers under the direction of Ballmer. The result of that was Windows 8.

I recall sitting in an all-hands once where the engineers were bleeding out their eyes about the abomination that was the new start screen, while the head PM just kept repeating, "This is the right decision. WE HAVE THE DATA."

Re:We promoted developers into architects without informing ... by antonvs on Friday November 20, 2026 @11:18PM (#50585901)
My headcanon is that the reactions to Ballmer's monkey dance and "Developers, developers, developers!" pissed him off, so he started to look for ways to make them less important.
Re:We promoted developers into architects without informing ... by 43920 on Friday November 20, 2026 @08:52PM (#50585040)
I've worked at one or two places that were like this, where I was expected to just do what the ticket said and not push back on anything. Thankfully, it's not too common, and most places I've been at seem to be pretty receptive of ideas traveling upward from individual developers to management.

Separately from that, pushing back is often uncomfortable and unrewarding. Even in places that do expect developers to have autonomy, it seems like there's usually some people that choose to just follow directions because it's easier and there's no consequences for doing so.

Re:We promoted developers into architects without informing ... by hibikir on Friday November 20, 2026 @09:57PM (#50585467)
This exists on certain large companies that rely on very cheap labor, ofter overseas contractors. You have 2 or 3 people who understand the system and are actually trying, and people who want to communicate via jira tickets, and care little about whether what they are doing helps the company in any way, or has wide repercussions. In those companies, a Claude agent is still cheaper, and more reliable.

At good firms that try to pay competitively, of course this doesn't happen much at all. But yes, it's unsettling to get to work, and have someone tell you that what they want is 3-4 well defined tickets that they'll write in the next two weeks, and don't want to engage even a little bit more.

Re:We promoted developers into architects without informing ... by Fr0styMatt88 on Friday November 20, 2026 @04:40PM (#50582605)
My jobs have always been the same, except maybe the first entry-level job I had out of uni. Even then, while I might not have been driving major architectural decisions, there was definitely _always_ the element of requirements gathering, verifying, etc. Never had a job in which someone has said "This is how it is to be done, no questions". There's _always_ questions even with formal requirements.
Re:We promoted developers into architects without informing ... by brightball on Friday November 20, 2026 @04:43PM (#50582647)
In 25 years I've only worked 1 place where there were truly architects handing structure down the chain and people were expected to just implement it...and it was a train wreck of an environment.

Every good place I've ever worked, the teams doing the implementation itself discuss it and agree on it in conjunction with some higher lead ensuring that there's no red flags to the implementation. If you're handing things down from on high, you're sending a lot of signals about what you think about the ability of the rest of your team...and none of them are good.

Re:We promoted developers into architects without informing ... by ratelimitsteve on Friday November 20, 2026 @04:54PM (#50582809)
I always thought of myself as a subcontractor under a GC. It's his job to make overall decisions, build blueprints, shit like that. It was my job to know the vagaries of plumbing well enough to either build what he told me to build or be able to articulate a really good reason why I can't. I might be the plumber one day, the drywall guy the next, the electrician on day 3, etc. Now with the LLM's help I'm the plumber for two hours, the drywall guy 'til lunchtime then I come back and I'm the electrician.
Re:We promoted developers into architects without informing ... by denkmoon on Friday November 20, 2026 @07:31PM (#50584411)
[delayed]
Re:We promoted developers into architects without informing ... by markus_zhang on Friday November 20, 2026 @10:32PM (#50585640)
It depends on what “architecting” means. In all companies I worked for, the fundamental architecture rarely moved. I added pieces or swapped pieces out, but we rarely made big, substantial architectural changes.

But if architecting means making decisions for anything, like how to approach any ticket, then yes we very often made decisions.

I had trouble aligning with the second definition and that was probably the reason I bombed a final round previously. The hiring manager asked what is my architecture experience, and I answered that we have principles and staffs so they usually architecture stuffs and we built on top of it. Apparently I should just boast about my 1000 “architecture” experience.

Re:We promoted developers into architects without informing ... by rtkwe on Friday November 20, 2026 @10:41PM (#50585679)
The division at my current job in the data and reporting world in fintech is architects get involved at the highest level on new projects or new patterns, basically strategic decisions approving novel implementations or doing POCs on them. Then down at the team level you have the tech leads and individual SWEs making decisions on how to build individual requirements.
Re:We promoted developers into architects without informing ... by omgwtfbyobbq on Saturday November 21, 2026 @01:11AM (#50586464)
Totally normal. I wouldn't say that architects were figureheads, but for the most part they did the majority of their work standing something up. Once it was running, system architecture was done by a mixture of developers, analysts, and business folks based on needs/wants and the reality/practicality of the system.

To be fair, I've also seen some pretty bad decisions by original architects/developers, although it's easy for me to criticize in hindsight.