I have tried all sorts of UI based workflow and orchestration tools over the last 20 years.
As someone technical, I start, I build something simple quickly but then start thinking edge cases, exception handling, alternate flows etc and suddenly all that is easier to handle in code directly.
Much of the power of these solutions is the pre made integrations into other systems, and not the flow control to someone technical. Once you realize that, you start looking for integration platforms and not workflow.
My common problem with all these visual builders is that they get too complex to maintain, all my workflows built with them are sitting there for years, I fear to touch them again. On the contrary the benefit these visual builders offer is the speed to get started, but with Cursor and Code Claude, it has become way easier to write a new workflow, comparable to visual builders for easy use cases, and even faster for complex use cases.
This is cool. Playground looks nice. Do you use yourself in your own flows? I am very interested to know your own use cases for it. I have found out that personal use cases of people who build tools like this are often the strongest.
I have tried all sorts of UI based workflow and orchestration tools over the last 20 years.
As someone technical, I start, I build something simple quickly but then start thinking edge cases, exception handling, alternate flows etc and suddenly all that is easier to handle in code directly.
Much of the power of these solutions is the pre made integrations into other systems, and not the flow control to someone technical. Once you realize that, you start looking for integration platforms and not workflow.
My common problem with all these visual builders is that they get too complex to maintain, all my workflows built with them are sitting there for years, I fear to touch them again. On the contrary the benefit these visual builders offer is the speed to get started, but with Cursor and Code Claude, it has become way easier to write a new workflow, comparable to visual builders for easy use cases, and even faster for complex use cases.
> it has become way easier to write a new workflow, comparable to visual builders for easy use cases
It didn't become easier to read one. And the trust to write one correctly is still limited.
This is cool. Playground looks nice. Do you use yourself in your own flows? I am very interested to know your own use cases for it. I have found out that personal use cases of people who build tools like this are often the strongest.
It runs in vscode and feels pretty good.
How different it is from node-red?