Glad to see disdain for "agile" is finally becoming mainstream. Now, it may be that someone writing rote software should follow a process, but for anyone doing anything actually innovative, you can't get into their head and tell them what process they must follow, whether waterfall or agile. It's like telling Michelangelo the process for sculpting.

Rather than teaching people processes, they should help foster better ways of actually thinking about the code itself. E.g., learning new programming languages and frameworks gives one a variety of perspectives to think about code from.