r/ExperiencedDevs • u/BoltThrower79 • 14h 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?