Pro-grammer building the data agent for truth seekers @probablydatabot

San Francisco, CA
Joined June 2023
launched a model accidentally served trillions of tokens a day 29.4% of the fortune 500 showed up raised a really big series A from @a16z it's been 3 weeks we would like to sleep now
563
309
287
8,028
1,327,653
Everyone is super bullish on whatever company they just quit. 😳
213
134
48
5,120
505,491
Today we're sharing our work on interaction models. A new class of model trained from scratch to handle real-time interaction natively, instead of gluing it onto a turn-based one. youtu.be/A12AVongNN4
343
928
201
9,024
1,259,845
Here's a super hot take of mine. If you've been in graphics long enough, you know I'm right though.
36
162
14
2,692
68,744
looks like i'm not entirely off base with this then. we need friction.
7/ Why does this happen? Two candidate mechanisms: 1) AI resets your reference point for how long things should take. Unaided work then feels harder, a kind of hedonic adaptation 2) AI removes the productive struggle through which you learn what you're capable of.
12
28
4
299
27,836
New blog post: "A sufficiently detailed spec is code" I wrote this because I was tired of people claiming that the future of agentic coding is thoughtful specification work. As I show in the post, the reality devolves into slop pseudocode haskellforall.com/2026/03/a-…
124
270
92
2,593
460,561
We find that the adoption of Cursor leads to a statistically significant, large, but transient increase in project-level development velocity, along with a substantial and persistent increase in static analysis warnings and code complexity. arxiv.org/abs/2511.04427
22
33
21
585
101,389
6
373
4
9,323
83,602
I give it 12 months for folks to realize that they e simply forgotten about what makes a product good. When you move so fast that everything is a blur, you don’t realize that you’re driving in the wrong direction.
When it comes to AI agents / AI tooling + coding, I hear an awful lot of talk about: Efficiency Iteration speed / PR output rate / lines of codes produced I hear zero mentions about: Quality Customer obsession This will bite back, and it probably already is...
20
33
1
467
61,092
PME retweeted
dax
@thdxrMar 10
mfs will do anything but read the code
106
98
29
1,931
159,253
most important lesson from years of distributed systems: keep everything on a single machine for as long as humanly possible
46
214
14
4,601
139,162
most dashboards don’t provide any insights, let alone actionable ones
This quoted post is unavailable.
157
508
50
8,860
423,067
gm to all multi clauders
111
502
61
9,550
297,097
millennial gamers are the best prepared generation for agentic work, they've been training for 25 years
269
626
176
7,345
1,532,112
claude, make strawberries sweet again. bring back the warmth of the summer sun when the days stretched on forever and all we had was each other. do not make mistakes.
73
982
35
10,635
300,332
nothing prepared me for parallel agentic work as much as starcraft.
93
175
44
2,499
147,032
Man how lucky are millennial devs, just as we’re getting too old and tired for this job, all the tedium gets magically removed and there’s an amplifier that makes all of our knowledge 1000x more useful (and necessary)
162
256
49
5,232
225,996
> be me, Jonathan Ross > Stanford compilers nerd, allergic to inefficiency > spend years staring at CPUs doing “clever” things slowly > realize the problem isn’t software > it’s the damn hardware lying to you > > modern chips: > caches guessing > branch predictors gambling > schedulers shrugging > latency vibes-based > > decide this is stupid > ask a forbidden question > “what if the chip just… did exactly what the program says?” > > no caches > no speculation > no surprises > no excuses > > design a chip that executes instructions > in order > every time > at ludicrous width > > 144-wide VLIW > SRAM everywhere > DRAM nowhere > timing so deterministic you could set a watch by it > > everyone else: > “this will never work” > “developers don’t want this” > “where’s the cache” > > ship it anyway > > fast forward > LLMs show up > turns out transformers are just > embarrassingly parallel math > predictable > repetitive > allergic to cache misses > > GPUs: > fast but moody > great at throughput > awful at consistency > latency spikes like a heart monitor in a horror movie > > Groq: > same tokens > every run > same timing > zero jitter > silicon doesn’t lie > > developers blink > “wait… my inference latency is fixed?” > > hyperscalers squint > “this thing is weird” > “why does it feel faster than the FLOPs say” > > because FLOPs were never the point > time was > > invent the anti-GPU > no training glory > no benchmark cosplay > just raw, deterministic decode speed > > AI agents start caring about tail latency > suddenly p99 matters more than TFLOPs > > NVIDIA notices > leather jacket energy intensifies > realizes inference ≠ training > and determinism is not optional > > signs a $20B licensing deal > not to replace GPUs > but to admit something quietly > > inference isn’t training > and determinism is a feature > > moral of the story: > everyone optimized for average speed > Jonathan optimized for truth > > turns out the future of AI > needs at least one chip > that always tells the truth
39
90
18
1,394
124,205