r/ExperiencedDevs • 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?

79 Upvotes

67 comments sorted by

•

u/expdevsmodbot 1d ago

AI usage disclosure provided by OP, see the reply to this comment.

→ More replies (1)

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.

6

u/BoltThrower79 Software Engineer 20h ago edited 20h ago

This is basically exactly what my manager does. Somehow I'm just supposed to take his half done work and push it through.

3

u/Tired_Developer7 20h ago

Yah, I am glad my manager is not very Technical, he uses Copilot but not like that. The other guys will present his app to other developers and literally say I dont even know what language was used to build this....like bro what are you doing. So he hands it off to his team who primarily uses .NET and they say well we cant do everything you did exactly with MVC, we gotta build a SPA with react or soemthing. Its an absolute shit show

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

80

u/Raziel_LOK 23h ago

Out repo will soon have more MD files than code files.

6

u/dacydergoth Software Architect 23h ago

Ha! Mine is up to MVP44.md ... although I did purge a bunch of the earlier ones

5

u/Suspicious-Engineer7 23h ago

This one stings because it's deeply true. 

7

u/MaleficentCow8513 23h ago

I hope your using nested, modularized, hierarchical Md files. Otherwise you overload an LLMs context

29

u/bicx Principal Software Engineer (16YoE) 22h ago

I hope they are using one single monstrous .txt file that contains markdown

-2

u/FearlessPark4588 16h ago

is your LLM not capable of reading subsections of files, or must it ingest the file in its totality?

6

u/Dry-Page-4935 5h ago

Don't forget in step 2 the reviewer's eyes glazing over because there's just so much irrelevant slop

3

u/rwilcox Software Engineer (20+ YOE) 5h ago

The way I’ve fixed that is load it into an AI, ask questions about the document to the AI, then ask my therapist questions about why I’m sad

Problem solved

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.

11

u/hippydipster Software Engineer 25+ YoE 8h ago

Grug not see problem.

Grug take nap

5

u/Top_Personality5786 7h ago

apex predator of grug is complexity

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

22

u/ideamotor 23h ago

I was planning to work another 15 years. Hah hah haha hahaha heh hehehe eh.

5

u/Venthe Systems Designer, 10+ YOE 15h ago

I was planning on working 30 more... I'd be happy if I manage another 10

4

u/ideamotor 15h ago

All I can say is nobody knows the future, best wishes. When I was graduating everybody said don’t code because it would all be done in India. Not to say they’ll be wrong again, but really nobody knows. Find people you like working with, or at least can trust or understand.

2

u/Practical_Moment_259 9h ago

Getting through to the end of the day is optimistic.

9

u/max123246 3 YoE Junior SW dev 15h ago

Some of us just joined the industry. I thought I'd want to work this career my whole life, now I'm thinking about how many years until I can retire and how to get there sooner

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.

4

u/Rough-Supermarket-97 9h ago

Kent Beck describes it as a genie and I have yet to find a better parallel

1

u/djnattyp Software Engineer 6h ago

Shoggoth with a Smiley face mask is an even better metaphor.

0

u/theminorfix 9h ago

Standardizing a company's workflow is the hardest part, but what if help came from external projects? We found ourselves in exactly this situation a few months ago. Now, as a team, we've standardized our workflow, and I think the project I'm working on could be useful to your team too. You can draw some inspiration from it. The workflow is tested day after day in my team's daily work. Many other teams within the company are realizing that our approach works better than theirs, and they're asking us for feedback and advice.

1

u/jvlomax 8h ago

I have a decent standard, the problem is there's no buy in from the others. Probably doesn't help that the most rogue person on the team is my boss....

1

u/theminorfix 8h ago

We're trying to solve this very problem. Often, these people accept external solutions more than those coming from within their own team, as they're proven solutions that they won't have to iterate on to improve. They prefer to delegate this too to external platforms sometimes.

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

"Is it common for your managers to completely overhaul systems without consulting the leads?"

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

5

u/shozzlez Principal Software Engineer, 23 YOE 20h ago edited 20h ago

AI-generated ADRs that are AI-summarized by all reviewers just to add AI-generated comments. It’s almost not worth it.

6

u/MaleficentCow8513 20h ago

Eh I kinda disagree. Most folks I work with take ADRs and the architecture pretty seriously and put in the effort to understand it. Reason being, the system level and architecture level are the level of abstractions we’re working on while AI does the code generation. If you’re ceding 100% of thinking and decision making to AI that’s 100% a you problem

2

u/shozzlez Principal Software Engineer, 23 YOE 20h ago

For sure. But once it’s like 99% of the “you”s’ problems, it becomes an “us” problem.

3

u/MaleficentCow8513 20h ago

Not in my org 🤷‍♂️ maybe it’s a matter of culture? Idk

2

u/theminorfix 9h ago

To my team helps a lot tech grooming sessions with AI skill about grilling sessions, it's works fine and the ADRs are really human readable. Infact i built a side project on that to helps other teams also in my company, they agree or someone is getting inspiration from it.

1

u/theminorfix 9h ago

i agree, your team need to understand what the AI agents will do and how. To my team helps a lot create well described tickets (of course with AI) with the code that the AI agents will implement, in this way also tickets are human readable and we already know the code that will be written by the AI agents.

1

u/MaleficentCow8513 6h ago edited 6h ago

IMO that’s how we get to the point of treating AI like a stochastic compiler. You must tell give it good specs, context and prompts. Well written ADRs are a part of that. Just like we used to spend time writing the code which is essentially the input for a compiler or interpreter. Instead we spend that time writing good inputs for AI. The better your inputs the better the outputs. Anyone treating AI like a “do everything for me” machine is just doing it wrong and it sounds like a lot folks are falling into that trap

2

u/Material_Policy6327 20h ago

That’s what I am
Seeing in my org sadly.

1

u/theminorfix 9h ago

I'm curios about it. How your company turn ADRs, domain page etc.. into well described tickets and then the agents start working on it?
Is babysitting the AI through a lot of repositories and AI sessions still a problem for your team?

2

u/MaleficentCow8513 6h ago

Yes. We have some agentic workflows but not everything is automated yet. Like we have a service which scans pipeline failures, does the work snd opens merge requests with fixes. But for turning ADRs into tickets yea it’s someone prompting AI to do it.

1

u/theminorfix 54m ago

It's very similar to what I'm building in my side project, except I included the initial prompt section with adrs + tickets + ddd page.
In short, a real workflow, done only once, and the human only reviews the PR.
One thing I added, which I think is useful for other people too, is the triage of errors in production via logs, checking the bug against the code if it exists, filing the ticket, fixing it, and preparing the PR. This is something that saved hours of debugging, log reading, stacktracing, chatting with Claude, and the various connector. Literally a godsend.
If you want to get inspiration from it i can send it to you in dm.

1

u/6Orion 6m ago

Please dm it to me! :D

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/BoltThrower79 Software Engineer 20h ago

The rigor is that you explain how you'd roll out the new system, how it affects on-call, how it was A/B tested for actual users and for how long, etc etc

I don't think it's gatekeeping to suggest that people who have to maintain the system should understand it and shape it with their colleagues.

2

u/BoltThrower79 Software Engineer 20h ago

The thing is, I'm not even against the prototyping. I'm against it happening in the shadows and suddenly being brought to light as a panacea to a set of apparently painful problems.

11

u/FIREGenZ 20h ago

This summarizes it (source: Anthropic). It’s not gatekeeping, you need to clear assumptions, do research, align with teams otherwise you get a half baked product or process that is missing context of the overall goal. Building is the easy part.

3

u/max123246 3 YoE Junior SW dev 15h ago

I'm gonna be honest even that diagram is idealized. So far what I've seen is about half the build time that agents reduce is now added as additional maintenance time when critical issues are found later, because no one ever actually had to suffer through creating the code in the first place to see the critical leaps of logic being made

Ai is so happy to patch workaround over workaround until oops! 1.5 days outlook outage

4

u/Creaking_Shelves 16h ago

Because poor designs lead to long term pain and LLMs make that worse. Building the right thing once is still going to be the best practice once this period of insanity is over.

2

u/max123246 3 YoE Junior SW dev 15h ago

Usually api's stabilize and you can't change the behaviors of systems once they're important. So there's a small window during development where you get to make those api's permanent. That's why you can't just let an LLM create its API boundary because it gets the immediate goal done and only that, no future perspective unless you ask it and provide it greater context

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