Hmmm.... True innovation isn't just about rejecting 'standardized methods' - it’s about knowing when to follow the rules and when to break them for better outcomes.

It's also possible to look at the problem the article raises from this angle. Suppose a junior programmer does routine work day to day (and routine work can be built on top of any framework - from machine code to no-code AI platforms; it doesn’t matter that much). Will that person continue to "do the job," or will they find a way out?

In this sense, a standardized learning experience can be somewhat justified. As usual, the urge "to be innovative" and master next level is a mix of innate traits and environment.