When to and when not to use return validators
We're changing our guidance for LLMs on Returns Validators.
6 of 391 posts
We're changing our guidance for LLMs on Returns Validators.
Consider this our declaration of permanent disengagement from “bar chart wars.” It’s good dev marketing, but it’s a waste of time.
So how did our marketing messaging get to where it is today? Let's go over all of the different things that we tried and the main lessons we took away from each iteration of Convex's messaging and design.
A Convex infrastructure engineer walks through the full push pipeline, from type-checking in V8 to atomic schema cutover, and traces a request through FunRun, the committer, and optimistic concurrency control.
Every GPU task I've run from a backend has the same problem: you fire off the job, then poll for results or wire up webhooks to know when it's done. This walkthrough shows a different approach.
Convex reran its evals with and without its AI coding guidelines to see if newer models still need 6,000 tokens of handcrafted rules to write good Convex code.