Pinned Tweet
Slop is code you dont read. And better models means more slop.
the solution? write sloppy tools to build stable systems.
but for the most committed people, go build new foundational systems. Rebuild github, rebuild tmux, rebuild database, and yes rebuild programming languages.
d the whole community for having us out at @aiDotEngineer
the solution? write sloppy tools to build stable systems.
but for the most committed people, go build new foundational systems. Rebuild github, rebuild tmux, rebuild database, and yes rebuild programming languages.
d the whole community for having us out at @aiDotEngineer
6
11
78
15,663
AI has 30x my average PR size over the last few years
the way you code has fundamentally changed.
the way you code has fundamentally changed.
1
0
9
591
“OpenAI worse than jev 🤡” feels like what they used to say about anthropic vs OpenAI
I benchmarked "Jev-killer" OpenAI Decisions API against Jev for HiringCafe.com, serving 2.5 million users. The task is to predict how relevant a user query/resume is to a job description, on a scale of 1-10. OpenAI is 2x more expensive and 5-10% worse. 🧵
0
0
0
383
Vaibhav Gupta retweeted
Everyone in AI is building for everyone else in AI.
We're building for your group chat.
Introducing Charming ✨ Personal apps for us normies.
Make an app for your book club, a meal planner for your family, go wild (it's free!)
Build in Claude/ChatGPT, share like a Google Doc
We're building for your group chat.
Introducing Charming ✨ Personal apps for us normies.
Make an app for your book club, a meal planner for your family, go wild (it's free!)
Build in Claude/ChatGPT, share like a Google Doc
132
66
397
521,835
what if you could ask a program any questions about itself as it was running?
coming to all baml programs near you 🐑
coming to all baml programs near you 🐑
1
1
18
922
Vaibhav Gupta retweeted
if only someone were building a programming language for this new era
DHH is fundamentally right about Rust. For context, Vercel has been undergoing a Rust-ification (carcinization, technically 🦀) for a while.
One of the first projects we migrated was Turborepo, from Go to Rust¹. The migration completed, but the RoI was actually quite controversial internally.
While Rust was in our eyes better for low-level OS access, something crucial for a build system like Turbo, the human migration costs were very sustantive.
Go is very fast. It's beautifully designed. It's easy to iterate on. We were very conflicted about the migration, because it was *humans* writing the code, *even if we knew Rust was a better choice*.
The calculus has now changed. What's "best for humans" is no longer necessarily "best for business".
FWIW, it's also quite unlikely that Rust is the end-all-be-all toolchain. I'm quite certain there's greener pasture ahead, because Rust itself was designed before the 'supersonic tsunami' of agents hit.
¹ https://vercel.com/blog/how-turborepo-is-porting-from-go-to-rust
0
1
6
1,229
why would you not have a faster app if you could? 🦀
Again, I'm not saying that all apps need Rust levels of performance. Far, far from it! But I am saying that if agents are really good at writing Rust, and you're onboard with agent acceleration meaning we don't read all generated lines, then it's a good argument for Rust!
3
0
9
1,167
we spend ~1 day every 2 months making our tests faster. we do this by:
1. removing tests we dont need
2. writing faster code
what triggers it? someone on the team gets tired of waiting for the clankers. this week it was @aaronvi
1. removing tests we dont need
2. writing faster code
what triggers it? someone on the team gets tired of waiting for the clankers. this week it was @aaronvi
2
0
16
2,090
javascript really is the zombie we keep dressing up
first typescript
then effect
now real types in typescript
first typescript
then effect
now real types in typescript
The first step is types.
We're adding a TypeScript-compatible type checker to Bun.
It’s the best shot ahead-of-time compiled TypeScript has at beating languages like Go on memory and speed.
3
1
47
8,187
it fascinates me that removing features still adds lines of code.
this is the worst thing about agents.
this is the worst thing about agents.
7
2
34
1,926
Vaibhav Gupta retweeted
Super fun chatting with @vaibcode @Dex about how we replaced BI with AI Agents we built in GrowthOS at Rippling
youtu.be/bGMiRmXbRUs?is…
youtu.be/bGMiRmXbRUs?is…
2
2
16
6,423
this man speaks truth
IMO the only tests you should have in the age of coding agents are, in order of priority:
1. Full E2E tests. Nothing mocked out at all. Can even be something that runs in prod on test accounts via Playwright or equivalent.
2. Integration tests. Agents make more mistakes as things bleed between data/API boundaries where schemas can drift.
3. Golden tests. This helps ground the code with real examples of data, and can be used as regressions against edge cases.
Unit tests are bloat 99% of the time if you’re using a frontier model since they’re smart enough now to get the implementation (and subsequent iterations) right on the first shot, so they only add bloat at this point.
6
0
35
18,447
now i get why people need 50 subs
We deleted 800k lines of unit tests from the @sazabi monorepo earlier this week.
Three hypotheses:
1- Unit tests "lock-in" slop code by making it hard to change or remove
2- Unit tests slow down dev cycles by making your agent do more work locally and by increasing CI times
ney by making your agent generate more tokens and by adding useless CI runs
Will report back soon with the results!
1
0
28
3,037