I don't think this blogpost is particularly revolutionary, it's fairly standard way of approaching things, but I also think I understand the gist of it. So the

I don't think this blogpost is particularly revolutionary, it's fairly standard way of approaching things, but I also think I understand the gist of it. So the author is somewhat of an consultant, and a company would approach them and ask "Which solution should I purchase?", and the author thinks it's a better approach to consider "What problems am I having?" first, and then which solution is needed becomes obvious. So Kubernetes is a solution to some problem(s), and unless you actively know and understand the problem you're trying to solve, you might go for a solution that solves a problem you're not having. Again, the blogpost is not presenting any new ideas, and seems to have been written on a subway ride home from work, but still the process described is useful in a lot of contexts. The TLDR of the blogpost is essentially: "customize solutions to specific problems rather than blindly adopting popular methods or technologies", or put another way "don't cargocult". That's basically the shortest version possible of this blogpost.