Staff Engineer @ Braintrust. All posts are my own. Formerly at Zapier (Sr. Engr), omcode (founder), Code RGV (founder), Google, UCLA (M.S. EE), UTSA (B.S. EE)

USA
Joined June 2008
There's still time! Come by to The Midway to attend: Builder Odyssey: AI Infra, Multimodal & FDE | Founder Demos & AI Film Showcase · Luma luma.com/seamate-tey7 I'll be sharing insights and lessons learned by building products for enterprise ai builders.
34
Olmo Maldonado retweeted
Your tokens have plans this Sunday 🤖 We’re bringing Builder Odyssey to SF on Oct 18—run, build, deploy, repeat. @H0wie_Xu @jfischoff @ibolmo @jove @zylberstein Grab your spot on @partiful 👇 partiful.com/e/0PAdTfFcp3hgB…
1
4
221
PSA: If a random security/permission prompts you to accept/deny, and you've got agents working. You *must* count to 10, and then check on the rascals. Days of auto accept (because you're the one tripping the detection) are long gone.
49
Guaranteed. AI would not be as successful if it wasn't for Markdown.
24
Olmo Maldonado retweeted
GPT-6.1 Sol promises similar performance to last week's GPT-6 release at one-fifth the token cost of Astra. Does it deliver? We re-ran our eval on how well models can guide users through multi-step problems. GPT-6.1 Sol reached 78.6% problem-solving accuracy at token prices far cheaper than Astra, Opus 5.5, or Fable 5.1. The most notable improvement was how the new model guided users through teaching interactions. Our "teaching quality metric" for GPT-6.1 Sol rose from 64.1% to 77.6%, compared to Astra's 82.2%. The results indicate GPT-6.1 Sol is able to interact with users in the ways they specify, leading to better pedagogy performance. Read more → braintrustdata.link/gpt-6-1-…
3
4
15
803
New tactic: One agent that only adds test (red team) to prove something is working or not working. Not allowed to edit non test code. Separate agent that only changes code (blue team) but is not allowed to edit tests. You're part of the red team.
59
Friendly reminder: Send Braintrust all of your data (text or binary) with zero/zip/nada of setup (no schemas). Brainstore will take it from there. You (or your agents) can retrieve with (un)structured calls virtually immediately. Now even faster.
We built Brainstore for the amount of data agents generate. Now agents are helping teams search through traces and run far more queries than a person would. Nitro is Brainstore's new asynchronous query execution engine. It separates waiting for storage from processing the data it returns, bypassing the limits of traditional object storage. We ran Nitro on more than 1 million real queries and found that full-text searches were over 2x faster. It's already on for Braintrust SaaS and BYOC customers. Read more → braintrustdata.link/nitro-bl…
3
119
Olmo Maldonado retweeted
We built Brainstore for the amount of data agents generate. Now agents are helping teams search through traces and run far more queries than a person would. Nitro is Brainstore's new asynchronous query execution engine. It separates waiting for storage from processing the data it returns, bypassing the limits of traditional object storage. We ran Nitro on more than 1 million real queries and found that full-text searches were over 2x faster. It's already on for Braintrust SaaS and BYOC customers. Read more → braintrustdata.link/nitro-bl…
3
8
6
42
11,115
Olmo Maldonado retweeted
We tested where Jev holds up as a judge. Jev was fast, cheap, and highly competitive for judging groundedness. But it lagged behind models with reasoning for math and code domains. Use it for certain eval tasks, but don't throw out your LLM-as-a-judge just yet. Read more → braintrustdata.link/jev-vs-g…
Jev from @typesafeai can replace your LLM-as-a-judge for scoring agent responses. It returns a choice or numeric result with information about uncertainty, so you don't need to spend time and resources prompting a general-purpose model into an LLM judge. Use Jev as a judge scorer in Braintrust and review its selected answer, confidence, and probabilities alongside the score. Trace Jev calls from your own application with the JavaScript or Python SDK. Read more → braintrustdata.link/jev-eval
10
4
38
4,615
Olmo Maldonado retweeted
Jev from @typesafeai is now available as an evaluation model in Braintrust. If you have an existing scorer, just change the model in the dropdown to Jev and reduce your scoring cost by 400x. We're very excited about this and are doing more of our own evals in the coming days.
Jev from @typesafeai can replace your LLM-as-a-judge for scoring agent responses. It returns a choice or numeric result with information about uncertainty, so you don't need to spend time and resources prompting a general-purpose model into an LLM judge. Use Jev as a judge scorer in Braintrust and review its selected answer, confidence, and probabilities alongside the score. Trace Jev calls from your own application with the JavaScript or Python SDK. Read more → braintrustdata.link/jev-eval
7
3
1
73
8,772
I've heard agents aren't good at product design. Try this: Assign a few agents to create criteria for X. Have a panel of agents score against said criteria. I'm expecting a score of 40%. Adjust criteria until the panel agrees with my score. Improve X until the score is 80%+.
1
2
74
After the first turn do: Adjust the criteria by modifying or adding new criteria. I'm expecting the score to go back down to 40%. Improve X until past 80%. Repeat improving the criteria and improving X until you can't bring the score down to 40% or if you've run 10 times.
1
26
Need to token max? Use "don't stop until". "Check the CI, fix anything we caused, and don't stop until the CI is green" "Use the feature specs and exercise them with Playwright MCP. Fix any findings. Don't stop until you've gone through all of the specs." YMMV.
78
Back in my day conflicts were avoided like the plague. Now with AI, I'm expecting Github to auto-fix conflicts with a suggested commit. For mavericks, maybe auto-commit the conflict fixes.
67
Make it part of your spring cleaning. Revoke everything.
1
2
96
I am but a mender of bad (AI) codes.
69
I've been testing letting the AI a "all" PR and for it to manage splitting up the PR and pushing changes done to the "all" PR down to each downstream child PR. A couple of lessons learned:
1
3
113
4. Human reviewers lack the complete picture. Include links back to the design docs, and help orient them what is the portion of this Manhattan project that you're working on. They're seeing the tree from the forest on purpose, but it is still jarring.
1
24
My takeaway: Take a backseat and focus on the right slices. Find the right size/scope to reduce time to merge/review. Focus on helping humans to pickup the context, and to help you improve the quality of the ship.
20