What’s the distinction you’re making here? To me it looks like you’re contradicting yourself, but I’m happy to admit I might be ignorant.
It’s a teaching tool in itself. You can essentially hire a janitor and make them an architect when everything just makes sense already and guides them in the right direction.
Which has always been my answer to over aggressive management strategies for "replaceable devs": If your product is fundamentally software, it will be as replaceable and disposable as your developers; Show some commitment instead and you will get it in return from worthwhile devs.
Employees perception of growth: it's easy to feel like you are learning more when it's something brand new because of how easy any topic is at the beginning, and you inevitably get more new things when moving; whereas pushing your existing abilities and strengths into incrementally more advanced areas is harder won and requires more fortitude. Also focus on short term financial gains over long term career growth: Although jumping ship has a tendency to force a re-align of financial reward with ability, it also resets your progress reducing your experience on long term project and denying yourself to opportunity to learn from the long term consequences of your decisions, which in turn can affect your long term prospects and financial rewards. (I am suspicious of candidates with a employment history of a series of short stints for this reason, because they did not have to live with the results of their output).
It's subjective, sometimes it's truly not worth staying, sometimes it is... but I suspect many people confuse short term gains with reasons to move, when their current job may in-fact be of more mutual benefit long term.
Of course eventually poor products are unusable, but I wonder if position on the barely-usable-to-snappy generates much revenue differentiation.
If you work at a company where the software you write isn't what generates revenue, you're going to have a bad time.
There are plenty of companies where developers are the profit centre.
Financially that reasoning makes sense but economically it’s stupid because you will end up with the same shitty uncompetitive product as everyone else. The developer counter argument is to just raise salaries, but over that past 2 years salaries have exploded and yet businesses have doubled down on this idea of prioritizing candidate selection and no training.
To your point about code quality I agree. I have an OS frontend written in JavaScript that fully loads (completes page render with state restoration) in under 200ms according to Chrome’s performance tool. The code is about 340kb unminified. You won’t that with React.