It could be that academics hold to the false notion of trying to adhere to design patterns everywhere, which hardly ever works in practice after the software ma

It could be that academics hold to the false notion of trying to adhere to design patterns everywhere, which hardly ever works in practice after the software matures and might only work a smaller/certain abstraction layers of the lifecycle of the software but then it breaks down and you're in no-mans land. The academia can also throw in many moronic notions of "how you SHOULD be programming" which is only a detriment really since how academics think you should programm has no relevance to how programming is like in the real world. Academical indoctrination and useless baggage basicaly.