Some feedback: show example input & output without requiring me to create an account. Looks interesting, best of luck!
Definitely fair feedback, we will look into it
Show HN: Turn any workflow diagram into compilable, running and stateful code
31–36 of 36 posts
Re: Show HN: Turn any workflow diagram into compilable, running and stateful code
#32This reminds me of the UML/RUP era from the early 2000s.... Is that an attempt to revive or even resurrect UML diagrams and Rational Unified Process blending it with AI? I would bet it's all dead forever. I'm skeptical about diagram-driven development making a comeback. In my experience, developers today prefer more agile, code-first approaches because requirements change rapidly and maintaining diagram-code synchron…
Code-first is kinda moving towards prompt-first. A diagram is just another way to prompt, so I can see this making a comeback, esp. with AI taking over more and more code.
Very much so, and in next iterations we will be expanding the scope both in what the generated code does as well as the ways to prompt
Re: Show HN: Turn any workflow diagram into compilable, running and stateful code
#33This reminds me of the UML/RUP era from the early 2000s.... Is that an attempt to revive or even resurrect UML diagrams and Rational Unified Process blending it with AI? I would bet it's all dead forever. I'm skeptical about diagram-driven development making a comeback. In my experience, developers today prefer more agile, code-first approaches because requirements change rapidly and maintaining diagram-code synchron…
This is a way to give developers and semi-technical people a way to generate and run code-first workflows using a visual language, be it UML or otherwise. We will be expanding support for text prompts in the future
Re: Show HN: Turn any workflow diagram into compilable, running and stateful code
#34Earlier quoted context omitted.
To make it less ambiguous, you could let the user describe the diagram with what the software is supposed to do in some sort of more rigid unambiguous reduced English /s
This would have the added benefit of being able to describe to the computer exactly what you want to happen and how. Feels like we're onto something here.
And them we can just use some process to turn those words into machine language. Maybe we can call it a compiler or an intepreter?
Re: Show HN: Turn any workflow diagram into compilable, running and stateful code
#35What is the difference with tools like Camunda (for BPMN) for example ?
Dapr is a code-first workflow engine that doesn't require a DSL language and includes many other integration points like pub/sub, service discovery and more. It also runs and deploys natively on K8s
So for workflows it's like Airflow, Brigade or hatchet or ...? How do workflows integrate with k8s (ressources, ...)? Camunda can also deploy natively on k8s. However you still develop apps for Camunda and it seems like dapr is no different there? Why is it in CNCF if it doesn't provide a way to build a workflow out of k8s-native artifacts (PVs, Deployments, Jobs, ...)?
Re: Show HN: Turn any workflow diagram into compilable, running and stateful code
#36Interesting. A future to consider, like it tries to understand our existing code(from GitHub or anyway) and generate new code that fits in well with what we already have?