HackerTrans
TopNewTrendsCommentsPastAskShowJobs

elijahbenizzy

no profile record

Submissions

Parallel, Fault-Tolerant Agents with Burr and Ray

blog.dagworks.io
1 points·by elijahbenizzy·2 years ago·0 comments

Lean Data Automation: a principal components approach

blog.dagworks.io
2 points·by elijahbenizzy·2 years ago·0 comments

Parallel multi-agent workflows with Burr

blog.dagworks.io
3 points·by elijahbenizzy·2 years ago·0 comments

Deep Dive on Hamilton Decorators

blog.dagworks.io
2 points·by elijahbenizzy·2 years ago·0 comments

Show HN: Updates on Burr (OS) – a full-stack AI agent framework

burr.dagworks.io
8 points·by elijahbenizzy·2 years ago·1 comments

comments

elijahbenizzy
·last month·discuss
Strands is more opinionated and higher-level, also not vendor neutral.
elijahbenizzy
·last month·discuss
wait till you see our other project github.com/apache/hamilton ;)
elijahbenizzy
·last month·discuss
So decorators here specifically attach metadata to make a function a reusable component. Builder makes a workflow. In Hamilton it's all decorators because it's purely declarative construction (sans reusability, really).
elijahbenizzy
·last month·discuss
Right it was a bit of a joke. Originally stefan and I presented frameworks when we were at stitch fix -- stefan called his "hamilton" and I called mine "burr". His was better for the use-case. But then we wanted to build something for state machines as opposed to DAGs, so we called it Burr. I wanted the git tagline to be "make your agents go burr..."
elijahbenizzy
·last month·discuss
Ha! We went all out on the modern one (user contribution!).
elijahbenizzy
·last month·discuss
This is where it's nice to have some guardrails -- coding agents work etremely well with limitations.
elijahbenizzy
·last month·discuss
Right I think this is why we made it unopinioated to a fault. Burr doesn't really do these things rather it just provides an orchestration framework. So it's pure BYO functions, classes, components, etc...
elijahbenizzy
·last month·discuss
Right -- possible it's slightly out of date https://github.com/apache/burr#-comparison-against-common-fr.... Good point on differentiating.
elijahbenizzy
·last month·discuss
One of the co-creators/maintainers here! Will try to answer Qs over the day.
elijahbenizzy
·last year·discuss
And then says... "you're welcome"
elijahbenizzy
·last year·discuss
Ok do this but for JavaScript
elijahbenizzy
·last year·discuss
This is amazing! I love that it requires very fancy hardware that is well designed. It's good someone finally made a chess game appropriate for the tiktok generation.
elijahbenizzy
·last year·discuss
Really excited about this! Congrats on the launch. Ships make sense as a first target, but I'm curious -- do you see a future in which we have household fission reactors? E.G. power an entire house (city block, etc...) with fission reactors?
elijahbenizzy
·last year·discuss
We’ve just learned that it’s possible to do AI on less compute (deepseek). if OpenAI doesn’t scale and that’s the problem then I’d argue that in the long run, if you believe in their ability to do research, then the news this week is a very bullish sign.

IMO the equivalent of moores law for AI (both on software and hardware development) is baked into the price, which doesn’t make the valuation all too crazy.
elijahbenizzy
·last year·discuss
This is one of those fun reads because it unifies quite a few things that I’ve read about or been interested in recently — Hilbert curves for geospatial indexing in dbs, Gray codes, and fractals! And it’s all fairly intuitive — the 1-bit shift makes sense for space traversal and makes the numbers curve pattern easier to reason about.
elijahbenizzy
·last year·discuss
Not believable, didn't read "double click"
elijahbenizzy
·2 years ago·discuss
We've leveraged Diataxis heavily for Hamilton and Burr documentation:

- https://hamilton.dagworks.io

- https://burr.dagworks.io

It's not always the easiest to follow (we often have disagreements about whether something is a tutorial or a how-to), but it's a really valuable framing and I think our docs have gotten better because of it.
elijahbenizzy
·2 years ago·discuss
Links to various resources + writeups!

Recursion/parallelism: - Docs: https://burr.dagworks.io/pull/370/concepts/parallelism/

- Example: https://github.com/DAGWorks-Inc/burr/tree/main/examples/para...

UI annotations: - Blog post: https://blog.dagworks.io/p/annotating-data-in-burr

OpenTelemetry: - Docs: https://burr.dagworks.io/reference/integrations/opentelemetr...

- Blog post: https://blog.dagworks.io/p/trace-all-parts-of-your-agenticai

Time-travel/forking: - Docs: https://burr.dagworks.io/concepts/state-persistence/#initial...

- Blog post: https://blog.dagworks.io/p/travel-back-in-time-with-burr

Monitoring: - Deployment: https://github.com/DAGWorks-Inc/burr/tree/main/burr/tracking...

- UI overview: https://blog.dagworks.io/p/burr-ui

And a few other writeups we're excited about: - Collaboration with instructor: https://python.useinstructor.com/blog/2024/07/11/youtube-tra...

- Full-stack example of a streaming app: https://towardsdatascience.com/how-to-build-a-streaming-agen...

- Human-in-the-loop app with Burr: https://towardsdatascience.com/building-an-email-assistant-a...