Diagram-based Engineering
Blog: Decision Management Community
Vincent Lextrait started an interesting discussion at LinkedIn about why “diagram-based engineering”, an approach Low code/No code belongs to, has been tried every 20 years, and always failed. “Just ask Grady Booch who co-invented UML. He’ll tell you that the failure is due to the fact that diagrams are inherently imprecise. Granted they are more precise than natural language, but they still fall short to capture the complexity of business applications. Nobody will try as hard as Grady. It’s just that the industry has forgotten now, it was 20 years ago (the same idea with flow charts 20 years before failed too). Oh you can deliver stuff, but it’ll be simple, not future-proof and you’ll enjoy short happiness. And bad performance. To reach the right level of finesse (and exceed it), you need text-based input: code. This is why math people invented their own language, because natural language was an obstacle to progress.” Link
Leave a Comment
You must be logged in to post a comment.
