rbranson

Joined 17 years ago

Karma
4,493
Submissions
1,237
Member since
Mar 8
currently floating in the ether.
View on Hacker News

Recent submissions

Comment · 5 days ago
The title buries the lede quite a bit:

> The Exponential Time Hypothesis is false

Comment · 1 month ago
Astra planner/designer with Sol+Luna subagents has worked well for me to improve context continuity. Luna generates code, Sol reviews code and runs/monitors integration/E2E tests. It's about 20% more usage efficient and 20% faster to finish tasks. I've been very subagent-skeptic for a while but the economics of codegen with Luna have made it click. This just works in Codex with a single-line AGENTS.md instruction.
Comment · 1 month ago
Assuming you are doing coding, I'm curious how would you characterize tne majority of your work (language, domain, frontend/backend, etc)?
Comment · 2 months ago
This is why wait-free and lock-free are separate concepts. Author is not claiming wait-free.
Comment · 3 months ago
For agentic use it impacts input tokens because the output is fed back into the model as input on subsequent turns.
Comment · 3 months ago
Comment · 3 months ago
it does not require training a model from scratch for it to be updated. the entire LLM training process is iterative. essentially each step (there are hundreds/thousands for a training run) yields a complete, usable model. tokens with updated data can be added on top essentially at any time in the future.
Comment · 4 months ago
You are correct. As a point of comparison: almost ten years ago at Segment we had a single Aurora PostgreSQL instance with ~50T of data, it was used to index potential identity data in a much larger corpus of files stored in S3.
Comment · 5 months ago
Comment · 9 months ago
Sure, but you still need to design around this problem. It’s going to be a happy accident that everything turns out fine if you don’t.
Comment · 9 months ago
Biggest thing to watch out with this approach is that you will inevitably have some failure or bug that will 10x, 100x, or 1000x the rate of dead messages and that will overload your DLQ database. You need a circuit breaker or rate limit on it.
Comment · 10 months ago
This is explicitly called out in the blog post in the trade-offs section.

I was one of the engineers who helped make the decisions around this migration. There is no one size fits all. We believed in that thinking originally, but after observing how things played out, decided to make different trade-offs.

Comment · 10 months ago
Comment · 1 year ago

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton