However, I really like his article because he applies some prioritisation which of the concepts are more important. (i.e. reducing dependencies and SRP ).
However, the other concepts of SOLID are still good to know and to apply. You should just not apply them as a only resolution to your problem.
And you will get into deep trouble if you violate LSP. Please don't.
I think in general you should not use depth-first to search for a tool to solve a problem. - Mix in some reasonable breadth first search (i.e. try a few other tools that could fit the problem. ). - Then look at the space, pick the best solution found so far, apply it, reevaluate. - If necessary refactor after learning more.
Also, i believe one of the most important problem resolution strategies that is missing: is to reformulate the problem into a problem that is easier to handle.