tarasyarema
Joined 8 years ago
Karma
142
Submissions
152
Member since
Nov 29
https://github.com/tarasyarema
View on Hacker NewsRecent submissions
Comment · 3 days ago
Founding and trying to exit a startup in Spain is definitely playing in Dark Souls mode...
Comment · 4 days ago
yeah, what we see is that the early users that love it actually are the ones that help spread the word more, the key here for me is how to expand this initial pool
Comment · 4 days ago
that's the golden question tbh, thinking on raising to help the initial growth tbh
Comment · 5 days ago
:D I guess it's like asking "how to get rich"
Comment · 11 days ago
Yeah I see this as what Cursor had a while ago where you would
open it and it would
have a different ui every time
Comment · 11 days ago
My take is that it should be ok to add scope, as far as you are ok doing huge cuts too.
Comment · 13 days ago
I think they do yes
Comment · 14 days ago
Just a fun experiment :D Code here https://github.com/desplega-ai/system-one
Comment · 15 days ago
It's not about trust, but rather the freedom of being able to move around providers. It's not even Devin, with the constant outages to anthropic and openai, being able to switch between them in a way that the system continues to work normally is key.
Comment · 15 days ago
Hi there,
Disclaimer: the blog should be glanced high-level as human, read the below instead. You can point your agents to it tho.
We've been working on agent-swarm (https://github.com/desplega-ai/agent-swarm) as an oss MIT project for a while.
One of the core principles on why we believe in is that when you adopt AI internally in your company, you should be free and not tied to a single provider (e.g. Devin).
Yesterday Devin introduced the Devin Oncall, and we wanted to replicate the feature in the swarm, but with one thing in mind: what if Devin is down?
As the swarm is built on top of a set of building blocks (not only agents), we created a set of workflow, deterministic scripts, and ui so that when a Pagerduty (or any other) comes it will handle it with automatic provider failover.
It's a simple thing really. In the blog post our swarm created explaining how to set it up you can see the high-level wf, and sub-wf.
If for some reason you have a swarm running point it to it. If you have some other system, do it too, as it might give you the high-level arch. to replicate it.
Cheers,
Comment · 22 days ago
If it does, it needs to be oss, that's why we went this way :D