There are technical decisions that sometimes dictate how the company is going to move forward a few years into the future, of course for the better...
For further actions, you may consider blocking this person and/or reporting abuse
How about the context (and examples) which is provided in the first paragraph? Maybe switching a frontend framework or the entire backend to something else? Technical decisions that took a significant amount of resources and time and would shape the company directions for years to come? Has it ever happened in your company? How was the process?
But thanks for the insights anyway! TIL about architects, I've never had that in my career.
Whoa, that is one roller coaster ride (in a bad way). Sadly, it hits too close to home for me. I wished that big technical decisions like these could've been handled better by the whole team. But I get that it came from the top (management/exec) then devs were just executioners. I'm surprised that the devs didn't say anything (maybe they did?).
Again, thanks for sharing, it means a lot to learn how others did it.