> Many 2005-era enterprise coding practices are still in very wide use for new projects
Just because something is older doesn't mean it's not still useful. Many developers these days hold an odd kind of logical fallacy that if something hasn't been done in the last few years, it's outmoded completely. Many concepts still hold high value dating back 40 or 50 years.
I agree completely that age is not a bad thing, and that "trendiness" is not really a good thing. ButWhenYourClassNamesStartToFollowThisPatternAndOutlengthSomeNovels, or your app compiles fine but fails at runtime due to the use of annotations and erased types, you might be using enterprise Java.
Just because something is older doesn't mean it's not still useful. Many developers these days hold an odd kind of logical fallacy that if something hasn't been done in the last few years, it's outmoded completely. Many concepts still hold high value dating back 40 or 50 years.