Developers don't hate visual workflows. They hate the magic.

Hey, I'm Ricardo. I've been building Flow Weaver , a TypeScript workflow compiler. I've been working on it solo for nearly two years as a side project, and I'm finally sharing it. Every workflow tool I've come across has asked me to leave my code behind. Use their editor, their format, their runtime. I never actually used them. I'd see the demo, think about what I'd lose, and close the tab. The thing is, I don't think developers hate visual workflows. I think they hate what they have to give up to get them. Your types, your linter, your version control, your ability to just read the code and understand what's happening. What if your code was the workflow, and the visual was just a view on top? The code is the workflow That's Flow Weaver . You write TypeScript functions, add one annotation, and the compiler turns them into workflow nodes. The visual representation is generated from your code, not the other way around. Step 1: Write your node functions These are plain TypeScript function