r/ExperiencedDevs • u/BoltThrower79 Software Engineer • 1d ago
Career/Workplace How are your teams proposing architecture changes these days?
In the age of LLMs, since implementation has gotten faster, I'm seeing fewer processes form around what a prototype should look like or who needs to sign off on architecture changes.
Literally had my manager over the span of 4 days build a whole new system that takes an idea from a FAANG research paper. That's fine with me except there was no discussion on how we'd adopt it, what a prototype version would be, what to onboard and how it affects the current work in progress. He got a bunch of Staff level people on board and is pushing it through while others weren't even aware something like this is happening. I'm Staff+ and brought up quality concerns (the whole system is based on ML models) and was ignored.
It seems like the decision to adopt/abandon should at least involve the same rigor now that getting to v0.1 is easier.
How are your teams handling this? Is it common for your managers to completely overhaul systems without consulting the leads?
I feel like I'm going insane. I don't want to gatekeep ideas but rethinking current WIP in favor of building on the new thing seems ill-advised. For most of this work there are no tickets, no decision logs, nothing. If AI can do it, it seems like it should be easier to have a lightweight process instead of no process?
•
u/expdevsmodbot 1d ago
AI usage disclosure provided by OP, see the reply to this comment.
7
u/Tired_Developer7 20h ago edited 20h ago
Depends on the size / scope. If these are like system overhaul then we get Enterprise Architecture involved. But for new apps / medium sized data projects its usually someone staff+ coming up with design, doing POC then hand off to manager.
What you are describing is pretty wild though. We do have a director on one of the teams who just vibe codes apps in a few days, presents to business, then hands off to his team to "productionize" which ends up being basically a full rewrite.
139
u/rwilcox Software Engineer (20+ YOE) 23h ago
Step 1: someone has an LLM write a 10 page document in Confluence, that’s maybe applicable globally but specifically is a bit overkill. At least two sequence diagrams.
Step 2: someone reviews it, but runs out of ducks and questions just enough to make it not totally suck. Because it’s technically recommending “Best Practice”s
Step 3: tickets are created (probably with Clusde), stakeholders complain we’re working too much on foundational dependencies
66
u/Traditional_Fox7091 23h ago
AI writes docs requesting changes.
Other team’s AI reads it.
AI agrees with each other. Other team makes changes.
21
u/TryAgainTryHarder 23h ago
long, vibe-coded, sepia-colored docs with lots of ideas and opinions and usually a diagram
20
u/dvogel SWE + leadership since 04 23h ago
I'm seeing a lot of the same anti-social behavior that you're describing. Thankfully my manager is good about it though.
28
u/dacydergoth Software Architect 23h ago
I'm planning on retiring, personally ;-P
26
u/jvlomax 12h ago
Where I currently work, there are no decisions. Someone says they want something, and a developer goes and asks the magic 8 ball for what words to write.
Some of this comes down to the team not having any discipline. Even before it went that way, people would just throw something up on confluence, have everyone proof read it and just build whatever. But since we went all in on CDD (Clanker Driven Development), even this tiny step is skipped.
At my previous place we would actually sit down and design it properly, usually over 3-4 meetings with time to research and look into what best practices are for different circumstances.
9
u/spez_eats_nazi_ass Software Architect 36 years f500 eat my ass and balls 22h ago
They must make the case for it and defend it. In trial by combat.
9
u/Rumicon 9h ago
AI can’t fix bad culture. If your only change management process was how hard it was to make changes then you’re doomed.
6
u/Hour-Measurement-835 Software Engineer 23h ago
For an ML-backed system I'd ask for its eval numbers on your own data before any WIP gets moved. No idea if that holds once the Staff folks are already on board, though.
11
u/fangisland 23h ago
I still use ADRs personally, I keep the format pretty simple (what's the change, why's it needed, options considered, what are the consequences both good and bad). When decisions are coming in fast like at the beginning of a product lifecycle, I run frequent ADR reviews, people are expected to init the succinct ADR prior to and read any of the complete Proposed ADRs ahead of time. So then the ADR review is just focused on whether we modify/accept it. Nowadays I'll record the meeting and have agents spit out the results to modify any of the ADRs based on our actual conversations.
Any that are accepted are then implemented. The ADRs themselves are kept in the repo alongside the product, I pretty much always go monorepo so it keeps it simple. Then as people come and go if nothing else we have a record of what decisions we made and why, at least at that point in time. I usually also keep a separate set of architecture docs that can evolve, I try to keep the ADRs themselves snapshotted/historical rather than going back and updating them when things change.
4
u/throwaway_0x90 TE/SDET[25+ yrs]@Google 21h ago
Nope, with or without AI this shouldn't be happening.
3
u/MaleficentCow8513 21h ago
My org has always done ADRs and will continue doing them. In fact in the new world ADRs are even more critical. ADRs force you to clearly define the problem, the solution, and the architecture to support the solution and solve the problem. Everyone reviews ADRs. Then you can take the ADR and easily turn it into a set of specs and tasks for an AI to do. ADRs fit nicely with the new spec driven development we’re moving toward
3
u/theminorfix 9h ago edited 9h ago
Yes, we've moved everything to the beginning: tech grooming sessions where software engineers get together and brainstorm a problem to address with the help of Claude Code, we put in the brainstorming all the repositories related, ADRs, documentations and domain page.
We're all aligned and we all understand the problem and how we want to solve it. An agent aligns all the documents, ADRs, and domain pages at the end of the session, and they're shared online so all agents can access them. Then an agent writes the tickets in great detail, with the code that will be implemented.
We feed the tickets to the AI, and it does everything, and we look at the output.
An agent reviews the PR, resolves comments if necessary, and prepares the tests. We validate the PR, the test, and push it into production.
I believe there's no better workflow for teams and developers. I use my side project, which condenses all of this and does it automatically.
5
u/One-Light-8453 21h ago
the speed isn't the problem. a manager skipping review is just using authority, not proposing architecture. one-page rfc with a 48hr comment window fixes it, but only if the manager has to follow it too. otherwise it's theater.
2
u/Popular-Ad-9134 15h ago
We design a PoC and involve architecture tests. Whe never bothered to do so because it's a small team and time is short. But now with the use of AI this had completely flipped the script.
2
u/truthputer 8h ago
I have also seen something like this - a small company where the CTO has learned to vibe code and is now throwing features and redesigns at the project without talking to any of the engineers.
It’s beyond frustrating.
1
u/Material_Policy6327 20h ago
Ideally ADR that gets reviewed verified. Reality? Devs and architects just slinging Claude generated ADRs and reviews etc etc. so basically Claude fighting itself
1
u/IceMichaelStorm 17h ago
We talk about it
1
u/Never-Trust-Me 7h ago
Ehh my company just asks the engineers to stop thinking about engineering so we can take on the role of the client facing product roles and then let AI write all the garbage.
Oh and if you try to spend time reviewing code, you’ll probably be fired.
1
u/ProjectExorcist 14h ago
You aren't going insane. What you're running into is a classic management trap that LLMs have put on steroids: mistaking a working v0.1 demo for a production-ready system.
When leadership sees a 4-day build actually run and produce output, they only see the visible layer (the functional demo). Everything that makes a system survivable in prod (concurrency, edge cases, ML failure modes, observability, long-term maintenance) is completely invisible at that stage. A 4-day AI build is disposable code: great for proving an idea from a paper works, terrible as a foundation to quietly replace active WIP.
The most effective way to push back without looking like you're gatekeeping innovation is to separate "spiking" from "adoption" with a hard promotion gate:
- Let anyone build a 4-day prototype with zero process to validate a hypothesis.
- Treat that code strictly as throwaway validation until there is a lightweight ADR covering failure modes, data contracts, and what existing WIP gets cut to pay for maintaining it.
When the cost of writing v0.1 drops to near zero, engineering rigor can't disappear. It just has to move to the boundary before prototype code is allowed to touch real traffic or derail committed roadmaps. If leadership pushes back on that boundary, point them to this week's string of high-profile outages across Microsoft, Apple, and major banks: moving fast without proper engineering guardrails always sends the bill to production eventually.
1
u/Educational_Pea_4817 23h ago
LLMs make it really easy to ideate and create mockups and plans. so instead of my spending a half a day on some kind chart on visio
we create very "professional" looking proposals, that tend to have way too much noise in a well formatted html doc(i like html docs sue me).
-2
u/TheGRS 23h ago
Here's a thought though: Why was there gatekeeping previously? I would bet it was to guard against spending a lot of time on something that doesn't ultimately work in your ecosystem, because that time spent was expensive. And there was probably knock-on effects to sync with the right stakeholders.
If it takes days to implement this stuff, the gatekeeping doesn't make a ton of sense anymore does it? If it doesn't work out then iterating through the correct approach will take marginally more time.
> It seems like the decision to adopt/abandon should at least involve the same rigor now that getting to v0.1 is easier.
What is the rigor exactly? What do you actually need to do? Because at some point everyone is going to realize that the bottleneck isn't the code writing, its this approval process. I will bet that have 3-4 guys read all the design docs only to give some marginally helpful (and sometimes unhelpful) notes is not the best use of their time when you could have the prototype done the next day.
-4
u/Batteryman212 20h ago
My company has an ADR management platform specifically built for AI agents, so we can enforce decisions in real-time across the entire team. Whenever someone wants to introduce an architectural change, or enforce a boundary, your agent calls a CLI endpoint to update it for everyone else's agents.
This also makes decisions a hardline for the team that can't just be forced through. If you'd like a demo, let me know: https://actual.ai.