A great way to avoid these manias is to constantly appreciate the importance of how a program is mechanically executed by the processor. For example, in OOP th

A great way to avoid these manias is to constantly appreciate the importance of how a program is mechanically executed by the processor. For example, in OOP that means do you know what vtables are doing in C++ or how method dispatch works in Java? In Erlang do you know why those linked lists are like that and how it interacts with the garbage collector? Do your functional constructs for the JVM spit out nice optimised code or are they spamming all over the heap? The moment people lose touch with these things they become highly susceptible to the nonsense that follows, as basically once you have made that leap everything is just magic.