It is part of why I think there's a future in tools that adjust with you. I've always thought about a tool like Microsoft Access or retool that will only handle simple cases. Then, it will allow ejecting into an app that uses industry standard tools with prebuilt tests. It's effectively a generator.
The goal would be internal tools. It could even start with a spreadsheet view that can "eject" to a simple app as things get more complex.
The same can be spoken about with any of the above technologies. If we can build limited small tools that can generate larger tools, we can solve many of these problems.
Especially yaml is overused these days. Kubernetes config or Helm charts (which in turn are also Kubernetes config) with hundreds or even thousands of lines are just horrible. XML with a decent schema would be a better fit - or to come back to the topic of the article: XML scales better.
The goal would be internal tools. It could even start with a spreadsheet view that can "eject" to a simple app as things get more complex.
The same can be spoken about with any of the above technologies. If we can build limited small tools that can generate larger tools, we can solve many of these problems.