I think you and the people disagreeing with you are both right, in a sense. These tools can absolutely simplify and improve even a small deployment…for someone with significant experience using them. But there’s a lot of learning that has to happen to get to that level of experience. And for a solo operator or small team without that experience, investing that time into learning may not be the best investment.

You see this contextual disagreement a ton here on HN. Those who gave taken the time to learn these tools and have practical experience using them for real deployments see the alternative as primitive, error prone and fundamentally limiting. Those without the experience see the tools as overly-complex distractions. Both are true, depending on your situation. Like almost all tech decisions, there are no universally correct answers. The best decisions are those tailored to the specific circumstances.

The more tools you have the more difficult it is to maintain yourself. In a larger team with dedicated DevOps you might be right. But in my case where I maintain frontend, backend, databases, security, hosting and the servers I cannot have too much complexity. And i find container tools too complex to fully understand as a full stack software developer (not an expert in anything). Same for heavy weight frontend or backend frameworks. I like to keep it simple without too many abstractions on all layers. So far I managed to build apps used by millions of daily users for about 10 years.

When there are just 9 servers and a single developer like in the article your opinion doesn't matter.

Is that some kind of universal truth or just what you think

It's not easy to maintain I can tell you