From an overview it seems more likely solvable with proper coding and tools, I love the fact that for example symfony/php makes you use a framework but you have the proper tools in order to forget that you're using the framework, you can have controllers, entities, repositories (and services with right extensions of framework services?), not depends on symfony, but also like if you use a framework and you go all in in getting it into your way, you would always end up by not being able to change stuff easily, even if it was your code, so I always make sure that I don't depend on things I can't change and have a set of interfaces layer in between "Depend on things you can change and not on things you can't", unless you made it perfect the first time and never end up changing it, but I think most likely this post is just junior point of view, with all due respect, I don't know the person, so maybe he's one of the best developers around, but just only considering this blog post, it seems very bad

Also I think the issue is more relevant with Python and django and ruby as they lack abstract classes and interfaces? in the context of making things incrementally changeable they're quite useful, so maybe there is something that is like that?