Embed Workflow (https://embedworkflow.com). Embeddable workflow builder for SaaS platforms. Your users design and run their own workflows inside your product.
5+ years now, bootstrapped. I still write most of the code. The product itself isn't AI, it's orchestration. Visual builder, triggers, delays, webhooks, execution logic. Some of our users do wire up AI models or agents through it, but the core is just helping non-technical people build automations for our clients product.
I'm building Embed Workflow (https://embedworkflow.com), an embeddable workflow builder for SaaS platforms. Your users design and run their own workflows inside your product.
Been at it for 5+ years, bootstrapped, small team. I'm a programmer first and still get to ship code daily. Also do demo calls every week. That's where I learn the most. Own product too and say no to features a lot. No investors either, which means nobody's breathing down our neck about growth.
Finishing up a workflow testing interface today. First time we've had one. I heard "this is industry standard! You need it" on demo calls forever, but nobody ever really pushed. Workarounds were good enough for our clients, and their users don't really care, they're mostly non-technical anyway. Regardless, the other night after putting the kids down I felt like knocking it out. I'll admit though, now that I have it... I wonder how I didn't do this earlier.
We're building an in-app workflow builder that SaaS companies embed directly into their platforms—letting their users automate processes without leaving the app.
Looking for a Support Engineer (10-15 hrs/week) to help developers integrate our product, troubleshoot issues, and shape our documentation. Technical background required—you should be comfortable reading code and understanding APIs.
Competitive hourly rate, flexible hours, real product influence. 1-2 month trial with path to grow as we do.
people want easier and if you hold a shiny object in front, most will lunge for it. Developers have been benefiting greatly for some time now. High paying jobs, no ceiling in business, praise from colleagues, respect from family, etc. Non-devs close to it now have this opportunity.
No one knows what the impact of AI code gen will be on developers. But if AI code gen under delivers and the demand on truly talented devs rise, then the ones 'doing the hard work' now and maintaining their craft by human coding will win big.
You're an early adopter, so you're seeing massive gains. But eventually everyone gets the same productivity boost and that becomes the new baseline expectation.
Any clever prompting techniques that give you an edge today will evaporate quickly. People figure out the tricks, models absorb them, and tools automate them away.
There's no substitute for actually coding to learn software development. For new engineers, I'd strongly recommend limiting AI code generation on real work. Use it to explain concepts, not do the work for you. Otherwise you'll never develop the judgment to know what that 10% actually is.
Malleable and opinionated aren't mutually exclusive. The best products that solve non-core business processes should be opinionated, that's their value prop.
But yeah, the demand for webhooks, integration options, embedding's will win IMO. I imagine more demand for API-first products.
good question. I think the community fell off and many plugins were left unmaintained. I was using it for over a decade up until recently. ST4 had so many plugin issues and it stopped being worth manually fixing.
For me, it was that the maintainer of a language plugin I used was, um, challenging to work with. I wanted to contribute to add some much-requested functionality and he talked to me like I was a toddler and warned me not to waste his time.
although I tried the collaborative features I unfortunately cannot say that I used these extensively for now. Although I found them quite nice, well integrated, seamless, and straightforward!
The issue is again people, they don't wanna change their _archaic_ workflow, stuck with inefficient -copy/paste- loop to the chat (ie. Slack) and back.
The story in the article went a bit too far that I agree, but I guess that is their north-star vision. Current implementation allows you to "join" a workspace session shared by someone, edit the same or different file, follow/watch a certain person, as well as have a chat (without requiring copy-paste) about certain piece of code. (both written or via voice)
If something, large enterprises generally don't support smaller and ambiguous licenses. Therefore, if Zed will allow enterprise licensing (ie. via on-prem license server or volume ordering, SSO, whatever) that would increase their adoption quite well...
For the record: I have never used the collaboration aspects of Zed
What I also have not used is vim emulation, though I have a vim background
As mentioned elsewhere, Zed is still very configuration-dependent to get the full power of it, and a lot of its functionality is never discovered for that reason
What pushed me to try it was Ollama integration which is not an afterthought, then I realized I loved it _way_ more than SublimeText, especially on performance, at first, then everything else once that won me over
I have ~10 running instances at any given moment, and >99% of the time never feel any lag, whatsoever
Another unexpected benefit is that terminals, code editor panels, and assistant chats, get to be sized and fit wherever you want, so it is also kind of a window manager... I often have more terminals open in Zed than in the Window Manager of the OS itself
> then I realized I loved it _way_ more than SublimeText, especially on performance
I currently have 19 instances of Sublime Text open, each to a separate folder containing a mix of C++ and Python code bases (some tiny some huge). Like ~8 of those have the clangd LSP plugin enabled. I don't think I've ever experienced lag in Sublime. KDE System Monitor is reporting 2.0 GiB of ram being using by sublime currently.
The clangd LSP plugin in Sublime isn't perfect, and it does occasionally break, and rarely spikes in CPU usage for no reason (although the editor always remains responsive). But, if I ever switch away from Sublime Text, I cannot imagine it ever being due to performance reasons.
I do all those same things in VS Code, especially the vim bindings, wouldn't give those up, but did recently leave the vim ecosystem because I had to spend too much time making the IDE work or enable features that are out-of-the-box in a code-oss based IDE
I give lots of feedback to Copilot in the hopes it makes the agents better in the long-run. I want them to read my code and train on it, along with the interactions with copilot, which is the next frontier in (post) training
5+ years now, bootstrapped. I still write most of the code. The product itself isn't AI, it's orchestration. Visual builder, triggers, delays, webhooks, execution logic. Some of our users do wire up AI models or agents through it, but the core is just helping non-technical people build automations for our clients product.