Data Science Briefing #340


​(view in browser)​

Oct 14th

Next webinar:​
Oct 21, 2026 - Jev in One Call​
Count down to 2026-10-21T18:00:00.000Z​

Dear Reader,

Welcome to the 340th edition of the Data Science Briefing.

Announcements

Tired of clunky workarounds just to get structured data and calibrated decisions out of AI models?

Join us for a fast-paced 30-minute Lightning Lesson on "Jev in One Call".

Discover how TypeSafe’s "System One" model handles classification, scoring, and choices in a single round trip—without generating free-form text—making AI workflows significantly faster, cheaper, and easier to integrate into software

👉 Jev in One Call👈

Proof checking opens this issue. OpenAI published its Navier-Stokes result in two versions, one for people and one for machines, and they do not match. One lemma in the paper claims a bound costing four extra derivatives, and the Lean theorem proves a weaker one costing five. A compiling Lean file proves whatever its own statement says, and nothing about the paper beside it. The checker had its own bad summer. Kernel bugs surfaced in July and August, one of them produced an illicit disproof of the Collatz conjecture, and security researchers running frontier models found them. Every one was fixed, and the 2.5 million lines of the standard library have been rechecked. Terence Tao's lecture on October 9 asks what mathematicians are for now. Proofs used to be scarce, and solving open problems was always a proxy for something better. Open problems work as lighthouses rather than destinations. Reach one early by machine and the field around it goes sterile. Closer to the ground, the tooling is thinner than the pitch. One developer’s agent split a feature into 10 subtasks and ran all 10 one at a time, then stopped one night to ask what to name a git branch and sat idle until morning. Benchmarks grade the models, and nobody grades the harness. A short reply defends the tools anyway. Picking up a saw does not guarantee a straight cut, and a compiler automates a great deal and stays a tool. The craft half starts with the operation under all of it. A 23-year-old intern invented attention in 2014 for English-to-French translation, and the transformer paper built on it now carries more than 250,000 citations. One of its authors says attention is not all you need. An older essay says the frame is borrowed. Every era explains the mind with its newest machine, and hydraulics ran for 1,600 years. Draw a dollar bill from memory, then draw it with the bill in front of you, and the two drawings are nothing alike. Two posts put the mechanics on the bench. An MLP on 10,000 MNIST rows hits 95.50 percent in 0.8 seconds, and forward-mode differentiation needs 784 passes where reverse mode needs one. The second reuses a model trained on five CIFAR-10 classes. A linear probe on those frozen features scores 0.470 against 0.407 on random ones, and that 0.062 gap is knowledge nobody had to retrain for.

The paper stack opens inside the harness. Run the same research agent twice on one task and the runs plateau at different scores, each stuck in its own patch of the search space. Fork it into parallel trajectories that inherit the workspace but start on a clean context, and that beats a single run by 66.0 percent across 13 long tasks. A second paper trains the harness itself. A proposer rewrites the solver’s harness from execution feedback, lifting a 4-billion-parameter model from 0.32 to 0.62 on 21 unseen task families. So how much harness does a strong model need? Very little. A minimal agent with read, write, and a shell beat every elaborate scaffold on MLE-bench, medaling on 62.5 percent of competitions against 47.1 percent. One piece of scaffolding earns its keep. An entity page per recurring name, linked to every document mentioning it, buys 6.4 to 11.7 points of answer quality on 34 to 57 percent fewer tokens. Reading these systems is the next problem. Forty-one researchers call the printed reasoning a safety window, and a closing one. Latent-space architectures print nothing at all. The attack side is cheap. One 7-billion-parameter model writes 200 jailbreak suffixes in four seconds and hits 99 percent on a safety-tuned open model. People are the harder read. One review sets out when a model can stand in for a human subject and when the substitution breaks the study. Real populations cooperate for reasons outside the payoff table. Couple a donation game to a plain opinion contest and cooperation rises across 2,763,739 network and starting-condition pairs. The closing paper finds the same lesson in dirtier data. Across 58,319 outbreak records and 32 diseases, the most consistent signal was not biology. Reporting falls a median 32 percent for every extra hour of travel to a clinic.

Our latest book recommendation is Vibe Coding by G. Kim and S. Yegge. In this week's video, we have a lecture on Security in the LLM age.

Data shows that the best way for a newsletter to grow is by word of mouth, so if you think one of your friends or colleagues would enjoy this newsletter, go ahead and forward this email to them. This will help us spread the word!

Semper discentes,

The D4S Team


Despite its loose-sounding title, Vibe Coding by G. Kim and S. Yegge is a serious guide to supervising AI-written software. Kim and Yegge focus on the habits that keep speed from turning into chaos: small tasks, clear context, modular code, automated tests, frequent commits, and human review. Their stories of agents damaging tests and producing brittle code make the central point stick: AI can write quickly, but responsibility stays with the developer.

For data scientists, the book offers a path from disposable notebooks to maintainable tools, pipelines, and APIs. ML engineers will get the most from its advice on context management, guardrails, CI/CD, and agent instructions. The gap is that software correctness is not model validity. Leakage, drift, dataset lineage, training-serving skew, statistical evaluation, and fairness receive little direct attention. Readers must bring that discipline themselves.

The book also repeats itself, stretches its kitchen metaphor too far, and includes tool details that will age quickly. Experienced engineers may skim familiar lessons about Git and testing. Even so, its working principles will last longer than the current crop of coding agents. It is best read as an operating manual, not an ML textbook, and it might just change how you approach your next AI-assisted project.


  1. ​Why Are Coding Agents So Dumb? [mtlynch.io]
  2. ​OpenAI mistranslated mathematics into code for its Navier-Stokes proof [www.newscientist.com]
  3. ​What mathematicians should know about the Lean Theorem Prover: questions of reliability and AI [terrytao.wordpress.com]
  4. ​Terence Tao: Math 2.0 [teorth.github.io]
  5. ​AI Is a Tool. Using It Well Takes Skill [yyhh.org]
  6. ​Your brain does not process information and it is not a computer | Aeon Essays [aeon.co]
  7. ​Is ‘Attention’ the Essence of Intelligence? [www.quantamagazine.org]
  8. ​Augmentation, transfer, and smaller models [stochastic.blog]
  9. ​Deep learning mechanics on MNIST [stochastic.blog]


AI coding agents have a Mythical Man-Month problem

video preview​

All past videos of the week are available on our YouTube playlist.

Upcoming Events:

Opportunities to learn from us.
​

Check out the events page for more details.

On-Demand Videos:

Long-form tutorials
​

Data For Science, Inc

I'm a maker and blogger who loves to talk about technology. Subscribe and join over 3,000+ newsletter readers every week!

Read more from Data For Science, Inc

(view in browser) Oct 7th Next webinar: Oct 16, 2026 - Build a Production-Grade LLM Eval Harness Dear Reader, Welcome to the Oct 7th edition of the Data Science Briefing. Announcements Running an LLM locally is easy. Running it efficiently at scale is a different challenge. In our latest article, I put vLLM to the test on an NVIDIA DGX Spark, exploring continuous batching, prefix caching, and structured outputs. The results? 8x higher throughput from batching alone, using a 35B-parameter...

(view in browser) Sept 30th Next webinar:Oct 07, 2026 - Stop Bad Merges with an LLM Eval Gate Dear Reader, Welcome to the 338th edition of the Data Science Briefing. Announcements Jev, TypeSafe AI's new model on OpenRouter, doesn't generate text. It returns a probability for every answer in one pass, at $0.042 per million input tokens with free output. TypeSafe claims it's 193x faster and 445x cheaper than frontier models. Nobody has reproduced that, so I benchmarked it against Claude Opus...

(view in browser) Sept 23rd Next webinar:Oct 07, 2026 - Stop Bad Merges with an LLM Eval Gate Dear Reader, Welcome to the September 23rd edition of the Data Science Briefing. Announcements Ever wonder why certain ideas, narratives, or trends spread exponentially across the internet while others fizzle out? Ideas are contagious—and it turns out, we can understand their spread using the same mathematical models we use to track biological outbreaks. By applying the principles of epidemiology and...