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

San Francisco, CA
Joined June 2023
Announcing Probably: the verifiable data agent We raised a $9M seed round led by @a16z and @Accel to build an AI agent that can ingest, transform, analyze and visualize raw data. Single take, unedited video analyzing 1B+ row NOAA weather data from Clickhouse 👇
21
15
6
94
29,727
LOL
I don’t think Jev will survive. @nvidia and @meta will release open-source Jev competitors within the next 30 days. @OpenAI will add a Jev-like endpoint to their model list in the next 60 days. And the rest of us will fine-tune custom classifiers that crush Jev and are 10x faster. In two years we’ll look back at this flash-in-the-pan and say “remember Jev?”
1
46
This take has take gone down history as the most thoroughly spanked ever
Jev will probably go down in history as the most thoroughly spanked startup ever — a brutal reminder of how few ways are are to create a competitive moat in software these days. (Hint: if you don’t have proprietary data that clearly distinguishes your offering then watch out.) 1. Launch a service that popularises a novel and valuable way to use LLMs 2. Watch literally everyone clone it almost instantly, in many cases beating it
55
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,029
1,326,927
Makes sense LLMs would "solve math" by hardcoding decimals That's exactly how they get the test suites to pass
1
56
AI launch -> AI scandal -> AI ... this is what they meant by loop engineering btw
1
55
Finally had to top up my Jev balance; paradox in full effect
53
The irony is that LLMs do the most architectural damage in reaction to test or lint failures RL is surely the blame for this
1
2
205
This is unfortunately also true of software design The syntax was never the problem
We instituted an official AI Writing Policy at @Clay. Massive thanks to @sophiebits on our engineering team who wrote this. Originally this was just for eng, but other teams found it so helpful we expanded it company-wide. Here are the four guiding principles: 1. You must stand behind every idea and sentence It is your responsibility to make sure that the entire document is representative of your own thoughts before you share it. 2. Writing is thinking Spending time on the writing process teaches you more about your topic. If you circumvent this process, you will walk away with a poorer understanding of the subject matter. 3. More time should be spent writing a document than consuming it If you generate a document from a short prompt then ask your readers to go through the longer output, you are disrespecting their time. They can talk to ChatGPT themselves if they want to. 4. Longer is not better AI makes it easy to generate long docs, and it loves padding them with sentences that say nothing. If you're producing docs from a short prompt, consider just sharing the prompt. You can read (and borrow) the full policy below. Hopefully we all communicate a bit more clearly now :)
82
The best part about building jevware is that we can just go back to calling "evals" ... test suites.
1
2
251
The biggest bull signal for Jev right now is the volume of smoothbrains trying to diminish it It is legitimate innovation and only a few people are realizing it The pendulum swing will be epic
2
88
not sure why people are worried about rogue AI YC is all missile companies now they'll take care of it
61
re: the AI doomer stuff LLMs are massively inefficient to run _in general_ let alone at swarm scale needed to sustain widespread damage therefore, it would be impossible to hide the source of a high profile attack long enough to avoid it being disabled by any number of means
1
1
126
therefore, risk profiling should focus more on early detection and response rather than prevention response is straightforward: block the traffic and/or cut the power
1
1
22
you can't coordinate slowing progress but you can coordinate detection and containment it has to be at grid and backbone ISP layers they don't have actual legs for the moment...
1
8
Anybody else getting some very weird internal thought leaks as output from Sol this morning?
2
70
Crazy how no matter how much I use coding agents my vim muscles never atrophy
1
279