6 ms·
Flowise was acquired by workday, so I'd take this with a grain of salt. However, I agree with the reasoning. I don't see a future for visual workflow builders.
by resiros 2mo ago
Flowise was acquired by workday, so I'd take this with a grain of salt.
However, I agree with the reasoning. I don't see a future for visual workflow builders. They are used to define plumbings that can be defined by a 50 line python script.
A non-technical user does not need to draw this workflow. They can just ask an agent to write that code for them, to debug it, to visualize it. All workflow builders now have an AI chat where you ask the agent to build the flow for you. Why not skip the flow part?
I'm pretty biased though since that's the thesis behind what I am building.
- Towaway69 2mo agoI would counter and say it’s understanding that makes the difference. Having an AI generate 50 lines of code that you assume will do the job is a little different to creating a flow that you understand and maintain. AI is really good at making everything seem so simple and easy, until it breaks. But then again, just use another AI to fix it. So then there is an agent orchestration layer for coordinating multiple agents with multiple personalities, role playing multiple parts in a comedy called software development. We still don’t know what they are really doing but does that matter? Does knowledge, experience, learning and failing even matter if AI is doing it for us?