jgraettinger1

6 ms·

1.
by jgraettinger1 6d ago
The best answer I’ve come to thus far is the model we (estuary.dev) are building out now: offering mcp.estuary.dev with tools for creating a sandbox with our CLI pre-installed, a tool for requesting that a tightly scoped access token be inj
2.
by jgraettinger1 4mo ago
At Estuary, we have an in-house Rust crate [1] for building scale-out durable actors / FSMs in Postgres. It powers all async activity in our control plane -- slews of fine-grain scheduled actions, complex change propagation through dat
3.
by jgraettinger1 4mo ago
The right metaphor isn't painting, though, it's molding clay. That first pass is slop, but it's raw clay that the agent is very good at molding given a modicum of direction and "not this, do that" comments. The comb
4.
by jgraettinger1 6mo ago
I ask Claude or codex to review staged work regularly, as part of my workflow. This is often after I’ve reviewed myself, so I’m asking it to catch issues I missed. It will _always_ find about 8 issues. The number doesn’t change, but it gets
5.
by jgraettinger1 7mo ago
I think there's a Danger Zone when planning is light-weight and iterative, and code is cheap, but reviewing code is expensive: it leads to a kind of local hill-climbing. Suppose you iterate through many sessions of lightweight planni
6.
by jgraettinger1 7mo ago
Maintaining a high-quality requirements / specification document for large features prior to implementation, and then referencing it in "plan mode" prompts, feels like consensus best practice at this stage. However a thing I&
7.
by jgraettinger1 11mo ago
As someone with workloads that can benefit from these techniques, but limited resources to put them into practice, my working thesis has been: * Use a multi-threaded tokio runtime that's allocated a thread-per-core * Focus on applicati
8.
by jgraettinger1 1y ago
It still doesn't make sense. Cursor undoubtedly has smart engineers who could implement the Anthropic text editing tool interface in their IDE. Why not just do that for one of your most important LLM integrations?
9.
by jgraettinger1 1y ago
> You can't do that for LLM output. That's true if you're just evaluating the final answer. However, wouldn't you evaluate the context -- including internal tokens -- built by the LLM under test ? In essence, the eval
10.
by jgraettinger1 1y ago
But that’s not good. You don’t want Bob to be the gate keeper for why a process is the way it is. In my experience working with agents helps eliminate that crap, because you have to bring the agent along as it reads your code (or process or
11.
by jgraettinger1 1y ago
Hi, I’m a cofounder / CTO of estuary.dev. Our whole mission is democratizing and enabling use of data within orgs. Open to a conversation about your work here? Reach me at johnny at estuary dot dev.
12.
by jgraettinger1 1y ago
I would recommend the `anyhow` crate and use of anyhow::Context to annotate errors on the return path within applications, like: falliable_func().context("failed to frob the peanut")? Combine that with the `thiserror` crate
13.
by jgraettinger1 1y ago
> Microsoft owns GitHub and VSCode yet cursor was able to out execute them Really? My startup is under 30 people. We develop in the open (source available) and are extremely willing to try new process or tooling if it'll gain us an
14.
by jgraettinger1 1y ago
> There's so many moving parts here. Yep. At the scope of a single table, append-only history is nice but you're often after a clone of your source table within Iceberg, materialized from insert/update/delete events w
15.
by jgraettinger1 1y ago
> On the other hand, one could argue that AI is just another abstraction I, as a user of a library abstraction, get a well defined boundary and interface contract — plus assurance it’s been put through paces by others. I can be pretty co
16.
by jgraettinger1 2y ago
The market is gobsmackingly huge, it's just the go-to-market entry points which are narrow. In my opinion, the key is to find a value prop and positioning which lets prospects try your service while spending a minimum of their own risk
17.
by jgraettinger1 2y ago
> To me the best solution seem like combining storing writes on EBS (or even NVMe) initially to minimize the time until writes can be acknowledged, and creating a chunk on S3 standard every second or so. Yep, this is approximately Gazett
18.
by jgraettinger1 2y ago
Roughly ten years ago, I started Gazette [0]. Gazette is in an architectural middle-ground between Kafka and WarpStream (and S2). It offers unbounded byte-oriented log streams which are backed by S3, but brokers use local scratch disks for
19.
by jgraettinger1 2y ago
One labeling is "organised crime". Another is: civil disobedience with a profit motive.
20.
by jgraettinger1 2y ago
> For example, imagine a high volume, low latency, synchronous computer vision inference service. I'm not in this space and this is probably too simplistic, but I would think pairing asyncio to do all IO (reading / decoding req
21.
by jgraettinger1 2y ago
> which is a total joke since it's often trivial to re-identify anonymized data HIPAA doesn't say ROT13 or anything else in particular counts as "anonymized". It's an after-the-fact assessment. If your "encr
22.
by jgraettinger1 2y ago
:wave: Hi, I'm the creator of Gazette. > But this seems quite brittle if multiple writers write to one journal and one malfunctions (aside from possibly failing to write a delimiter, there’s no way to tell who wrote a record, and us
23.
by jgraettinger1 2y ago
Or, it can be self-evident to all that today's work can deliver more benefit if focused elsewhere, instead of root-causing fickle alert flakes. Customers buy products and services, not alert hygiene.
24.
by jgraettinger1 2y ago
The first place I'd look is using binary search over a sorted `Vec<(u32, u32)>`. The `superslice` crate is handy for this, or just using the built-in binary search methods. The improved cache behavior alone can make an order-of-m
25.
by jgraettinger1 2y ago
Companies have internal processes and typically can’t say “here’s an extra 5k for saving our butts!” unless there’s an existing program and money set aside for such spot bonuses. It’s a huge audit risk. If your management is good, it absolu
26.
by jgraettinger1 2y ago
PostgreSQL. The WAL is an event log, and when you squint at its internal architecture, you’ll see plenty of overlap with distributed event sourcing.
27.
by jgraettinger1 2y ago
The key ingredient is leveled reads across topics. A task which is transforming across multiple joined topics, or is materializing multiple topics to an external system, needs to read across those topics in a coordinated order so that _does
28.
by jgraettinger1 2y ago
NOTIFY drops events on the floor if no session is currently LISTEN-ing (due to a consumer restart, say). You could use a trigger to write events into a log table from which they're reliably consumed and then removed, but you've no
29.
by jgraettinger1 3y ago
This comes from a place of love and empathy -- I've been here, am here, and will be here again -- but this realization reads like the first step in the long, long road from prototype to product.
30.
by jgraettinger1 3y ago
Our (Estuary; I'm CTO) streaming transformation product handles this quite well, actually: https://docs.estuary.dev/concepts/derivations/ Fully managed, UI and config driven. Write SQLite programs using lambd

More ›