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.

[–] ganymede@lemmy.ml 1 points 1 year ago* (last edited 1 year ago)

agree 100%

have also noticed an uptick in "new is always better, those old ways are so dumb and they were so stupid" mindset.

not sure if this is directly part of the reason, but the upshot is you don't need to learn the fundamentals. you're protected from learning how things actually work, because there's always a bloaty house of cards chain of libraries to keep you separated from reality.

and of course its always easier to write off all of the fundamentals as 'pointless old garbage', than actually challenge yourself with any of it.

then you can enjoy a false sense of superiority, not because you overcame anything, but by never even trying.

"undefeated", not because you ever won, but because you never fought.

and its not the "kids these day's" fault. training institutions are corrupted by greedy suits, its all about the $$$s and pumping unprepared grads out at a blinding rate is more profitable (short term).