Slowly and surely, we relearned all of the lessons the mainframe designers had learned, and it became heavyweight.
The new generation is working on smaller problems and saying, "This is heavyweight!" And then they go with a minimalist solution, and the problem space grows. They then learn the lessons the crotchety senior programmers had told them.
Microservices is but one more example. Decrease coupling, increase cohesion. And then they'll get into hairier and hairier problems and rediscover the problems the last time someone tried it. Remember when service oriented architecture was the buzzword? :)
To be fair, each generation iterates on the past. I'd rather code today than the 80s. However, each generation, each programmer has to learn the lessons again.
Usually, we learn the hard way.
When I first encountered OOD, I lapped it up and became an acolyte. Then I discovered how OOD didn't actually solve ALL problems well. Now I consider myself post-OOD; I use the parts that are useful when they're useful, and otherwise I use other paradigms. I became a fan of and later gave up on Ruby as a language before Rails existed.
I don't think I've ever been the junior programmer you just described.
"Oh hey data hipsters, no I'm sorry our SQL data base is 200TB, no we don't have performance problems."
"Oh no we don't need your functional restless framework, we've been using a java framework for like 10 years, it peaks out at 1000 req/s."
"Why would we buy 4 webservers? It has 4 nics, and 8 CPU sockets. Sure it costs 500k each, but then we can keep using our java framework."
[1] https://en.wikipedia.org/wiki/Object-oriented_programming#Hi...
I also used to work with these a long time ago (EJB 1.1 and 2.0). A lot has changed since then though, and EJB 3 has solved a lot of the pain points (arguably pushed by the success of concepts used in Spring and Hibernate, whose authors served in the JCP for the newer JEE specs).
I kept reading, looking for the punch line, but as far as I can tell he's just describing really basic information hiding and interface design.
Maybe it's OOD For Server Programmers? There's nothing wrong with it, it's just surprising to me that it's news.