Any "architect" joining the company and pushing for drastic changes like that is either an idiot chasing the hype, or a malicious actor trying to boost their importance.
Good news: your gut feeling is correct.
Bad news: you will likely lose this battle, unless you're good at playing company politics.
Here's how it typically goes:
1. A new lead/architect/manager joins the company.
2. They push for a new hyped technology/methodology.
-> you are currently here <-
3. The team is split: folks that love new things embrace it, folks that care hate it, rest are indifferent.
4. Because the team is split, the best politician wins (usually the new hire).
5. Switch happens and internally you know it's fucking disaster, but you're still forced celebrate it.
6. When disaster is becoming obvious people start getting thrown under the bus (usually junior engineers or folks that opposed the switch).
Good news: your gut feeling is correct.
Bad news: you will likely lose this battle, unless you're good at playing company politics.
Here's how it typically goes:
1. A new lead/architect/manager joins the company.
2. They push for a new hyped technology/methodology.
-> you are currently here <-
3. The team is split: folks that love new things embrace it, folks that care hate it, rest are indifferent.
4. Because the team is split, the best politician wins (usually the new hire).
5. Switch happens and internally you know it's fucking disaster, but you're still forced celebrate it.
6. When disaster is becoming obvious people start getting thrown under the bus (usually junior engineers or folks that opposed the switch).