


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


Elegant
Daniel Lemire @lemire Oct 27 Article Billion-query-per-second lookup tables in C++ A lot of software spends its time mapping strings to values. A web server must identify the HTTP method (GET, POST, ...). It must recognize header names. A URL parser must recognize the protocol


gold
despite the unfortunate timing, we take disclosures seriously at @typesafeai at approximately 6:49PM this Friday evening, we became aware of a massive unauthorized leak of ALL customer noul outputs in effort to maximize transparency, here is the link: gist.github.com/diogo149/810…

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?”

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

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

Makes sense LLMs would "solve math" by hardcoding decimals That's exactly how they get the test suites to pass



AI launch -> AI scandal -> AI ... this is what they meant by loop engineering btw

Finally had to top up my Jev balance; paradox in full effect

The irony is that LLMs do the most architectural damage in reaction to test or lint failures RL is surely the blame for this

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 :)


The best part about building jevware is that we can just go back to calling "evals" ... test suites.

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