4 ms·
I think it's kind of like the AI Winter -- there was a period of time when the software industry really went down a stupid path in regards to diagram-based code
by charlieflowers 4y ago
I think it's kind of like the AI Winter -- there was a period of time when the software industry really went down a stupid path in regards to diagram-based code generation. A lot of kool aid was drunk over promises of making it so that everyone would be able to program.
But, of course, it turns out, someone still needs to understand and be able to debug all the nuances that makes complex logic systems complex, especially when they're cobbled together from many underlying systems.
The real goal should be to take good programmers and magnify what they can do. But since the industry bought so hard into the naive vision, the industry is behind where it should be on a smarter vision.
- rjsw 4y agoThe OP is asking for diagram generation not code generation.
- tehbeard 4y agoWhich are two sides of the same coin, transformation of code <-> Diagram. The industry couldn't get the simple one of those (diagram -> code) to work well enough, how would they do the much more complex reverse? Architectural and even library nuances can't be easily quantified to a particular UML symbol unless you go through the effort of classifying it for every library/design pattern, and keeping that up to date as well.
- mattm 4y agoNot really the same thing. With diagram generation, the code is still the source of truth. There would just be a way to automatically visualize it. With code generation, you would program by diagramming up front and then the code would be generated from that.