This really grinds my gears especially when working with the junior devs. They are always preaching about this new hot library and tried to refactor the whole app based on this cool article written by some well known developer. When I asked about their reasoning behind the chance they’re only able to link the blogpost made saying that X is bad and Y is the way going forward. I asked them what situation where they actually cannot solve an issue using X in a project and whether they can prove that using Y is the panacea for all of our woes, they all go silent.
Afterwards I always tell them it’s fine to look for new ways to do things. But before you go to try to propose such a big change at least write some PoC demonstrating the strength of the new thing when they have some downtime.
This really grinds my gears especially when working with the junior devs. They are always preaching about this new hot library and tried to refactor the whole app based on this cool article written by some well known developer. When I asked about their reasoning behind the chance they’re only able to link the blogpost made saying that X is bad and Y is the way going forward. I asked them what situation where they actually cannot solve an issue using X in a project and whether they can prove that using Y is the panacea for all of our woes, they all go silent.
Afterwards I always tell them it’s fine to look for new ways to do things. But before you go to try to propose such a big change at least write some PoC demonstrating the strength of the new thing when they have some downtime.