Weirdly this is pretty much the story of code generators. When I first got into web development there were people using HTML generators based on photoshop comp

Weirdly this is pretty much the story of code generators. When I first got into web development there were people using HTML generators based on photoshop comps. They would produce atrocious HTML. FE developers started rewriting the HTML because otherwise you'd end up with brittle layout that was difficult to extend. By the time the "responsive web" became a thing HTML generators were dead and designers were expected to give developers wireframes + web-ready assets. Same thing pretty much happened with UML->Code generators, with different details. There's always been a tradeoff between the convenience and deskilling involved in generated code and the long term maintainability. There's also the fact that coding is fundamentally an activity where you try to use abstractions to manage complexity. Ideally, you have interfaces that are good enough that the code reads like a natural language because you're expressing what you what the computer to do at the exact correct layer of abstraction. Code generators tend to both cause and encourage bad interfaces. Often the impetus to use a code generator is the existing interfaces are bad, bureaucratic, or obscure. But using code generators ends up creating more of the same.