3 ms·
> A lot of younger developers like to come into a new project and slap on the latest frameworks or coding practices that they've picked up recently, without ack
by HumblyTossed 2y ago
> A lot of younger developers like to come into a new project and slap on the latest frameworks or coding practices that they've picked up recently, without acknowledging that breaking the standards of the project lead to higher mental load to maintain that code over the long term.
This is an organizational problem.
- chamomeal 2y agoRight. At my new job, the framework-level choices come from people like 4 levels above me. Problematic for a lot of reasons, but juniors slapping frameworks onto things is not one of them. I’m actually kind of struggling to imagine a scenario where a junior developer has the agency to slap entire frameworks onto existing systems. Maybe a late stage startup? Coding practices, definitely.
- doublerabbit 2y agoEnterprise. We are currently going under modernisation converting Perl to Python. It's what it is, but I've encountered developers coming along and wanting to throw bulky frameworks at when all you require is to process the output result of a vendor issued binary. There have been novel ideas but just unpractical for the causes. It's madness getting through to them when all you require is a replica of the current system and not a rewritten feature set not related to the scripts at hand.