It would seem that popular software practices are trending away from certain types "premature flexibilization." Conventional Java coding practices - things you

It would seem that popular software practices are trending away from certain types "premature flexibilization." Conventional Java coding practices - things you might have seen everywhere a decade ago - might call for a number of interfaces, class hierarchies, and perfunctory design patterns (getters, setters, perhaps factories) just to declare a SINGLE concrete class. These days we're much more accustomed to succinct code in dynamic languages and looser structural rules. Maybe some of this strict enforcement has shifted off into test suites. The author's observation that anticipating changes / future requirements in software is often misguided and ill-informed fits right into this trend toward simplicity. Concise, readable code that's easy to shuffle around is much better suited for adaptation than a big, bulky "framework" that tries to anticipate every contingency.