At the opposite end of the global scale, I've often seen new (young) employees, arrive and immediately start suggesting sweeping changes.
We're using the wrong language, the wrong source control, the wrong methodologies, the wrong libraries, and so on.
If the flavor of the month is say BoringSSL we should be working to switch all our code from OpenSSL and so on.
Usualy it takes a bit of effort to bring them up to speed. There are positives and negatives to all choices. Usually I assign them the task of coming up with 5 downsides to their suggestions.
Articulating the downsides helps to show you understand the whole impact of an idea, and thus aren't making a "buying the koolaid" decision simply based on popular opinion.
We're using the wrong language, the wrong source control, the wrong methodologies, the wrong libraries, and so on.
If the flavor of the month is say BoringSSL we should be working to switch all our code from OpenSSL and so on.
Usualy it takes a bit of effort to bring them up to speed. There are positives and negatives to all choices. Usually I assign them the task of coming up with 5 downsides to their suggestions.
Articulating the downsides helps to show you understand the whole impact of an idea, and thus aren't making a "buying the koolaid" decision simply based on popular opinion.