V retweeted
New research shows test-time communication between multiple agents allows scaling gains to compound, matching k independent agents with fewer agents and outperforming human baselines on c…
arxiv.org/abs/2609.21032
#MachineLearning #AI #LLM #DeepLearning #AgenticAI
V retweeted
When Michael Levin (@drmichaellevin) planned to change the voltage of embryo cells, someone wrote to his postdoc mentor saying he’d had a mental breakdown. Membrane voltage was thought to be mere housekeeping. Then a graduate student found the embryos covered in black dots. They were eyes.
Full episode: youtu.be/c8iFtaltX-s
V retweeted
Reminder: all that gradient descent does is store memories in weight vectors by superposition.
arxiv.org/abs/2012.00152
V retweeted
This was great fun!
I put four longevity titans in one room for an hour, and they gave me four very different answers on when we’ll beat aging.
They challenged each other on timelines, the FDA, AI, and the hype problem in longevity science.
Watch @aubreydegrey, @biogerontology, @geochurch, and @M_S_Ringel battle it out, live now on The Beyond Tomorrow Podcast!
Andrej Karpathy’s Small LLM Setup PDF:
drive.google.com/file/d/1Aw6…
V retweeted
Could the Body Be Thinking Before the Brain Exists?
The most mind-blowing implication is that intelligence may be far older than brains: morphogenesis behaves experimentally like goal-directed problem solving, because cells can coordinate, detect deviation from an anatomical target, and change their collective behavior until large-scale form is restored, suggesting that cognition may begin wherever living systems can represent a preferred state, measure error, remember enough history to respond, and act across many possible routes toward the same outcome.
The philosophical shock is that agency can scale: one cell pursues local physiological goals, electrically coupled cells pool those limited competencies, and the resulting tissue can pursue anatomical goals that belong to the collective level, so your body can be understood as a hierarchy of nested problem solvers in which communication enlarges the radius of concern, turning microscopic cellular preferences into macroscopic objectives such as building, maintaining, and repairing an entire organism.
The deepest consequence is that minds may be evolutionary descendants of body-building intelligence: mechanisms that once coordinated cells through anatomical space could have been elaborated into nervous systems that coordinate action through behavioral space, which means the conceptual boundary between development and cognition may mark two expressions of one older control architecture, and consciousness research may ultimately need to ask how far a system’s goals extend before asking where its mind begins.
Replying to @iambrunocoelho
One important thing. I do not *define* morphogenesis as a problem-solving process. You can't make such claims by definition, you have to do experiments and find out if that's what it is. Turns out, it is. Here's an overview: thoughtforms.life/biophysica…
V retweeted
Replying to @iambrunocoelho
One important thing. I do not *define* morphogenesis as a problem-solving process. You can't make such claims by definition, you have to do experiments and find out if that's what it is. Turns out, it is. Here's an overview: thoughtforms.life/biophysica…
V retweeted
We'll be spending a lot more time trying to understand the outputs of language models. A few thoughts, tips & tricks:
Writing. Something I've had success with: Ask your LLM to explain something in ASD-STE100, it's a controlled language specification originally developed for aerospace maintenance documentation. LLMs well-versed in this language and it comes with heavy constraints on clean writing style that I often find a lot more readable. Sometimes I've tried to soften it a bit e.g. ask for "80% of the way to ASD-STE100" because the spec is quite stringent. But even better:
Diagrams / images. Instead of writing, ask your LLM to create a diagram. These can be a lot easier to process, parse, and understand. But even better:
Web pages. Ask for output "in HTML" to get a beautiful, interactive webpage. LLMs are getting really good at frontend and can create beautiful experiences, animations, etc. But even better:
Explainer videos. The output format I am most bullish on is fully custom / bespoke explainer videos generated on any arbitrary topic. Experiment with things like "Create a 3b1b style video explainer on X. Use my ElevenLabs API key for audio narration". (you'd need an API key for the latter or you can ask your LLM to find you decent free alternatives that use your local compute). This is actually starting to work!
In summary:
- As LLMs get better, they will do more and more of the legwork autonomously, and a lot more of our work will rise up the abstractions into oversight and understanding.
- Luckily, LLMs can help here too because as intelligence and code are increasingly abundant, you can ask for large, custom, discardable software artifacts (e.g. web apps, video explainers) that would have never made sense to create before. Push the boundaries here and you'll be surprised.
V retweeted
Oct 2022, five weeks before ChatGPT, #futurist Ursula Eysin told me that predicting the future is a powerless position. Her answer is #ScenarioPlanning. Her #AI take reads differently now, and so do her 3 rules for turning #uncertainty into an advantage.
snglrty.co/4bm53UK
V retweeted
I don't read/write code these days, I only instruct an LRM. But it's not because I think LRM code quality is perfect, or even good. And it's not because I think my instructions are always being perfectly acted upon -- I know they aren't.
The thing is: LRMs don't just write your code, they unlock new ways to control what you're doing and maintain understanding of your system, which are about as effective as reading code. You can better test your codebase, you can audit specific components, you can spin up visualizations, you can ask the LRM to red team, etc. You can do all of these things at high speed -- you couldn't before. The benefits of reading/writing code can now be achieved in new ways.
All in all, the ROI of writing code by hand is no longer looking good, not because LRMs got perfect but because they're so fast at doing things that you can develop new workflows around them, workflows that end up being more productive than the old workflows.
We don't talk enough about this, but the database we've always known is dead.
Modern applications need to store structured data, JSON documents, relationships, vector embeddings, spatial data, and text.
So far, the solution most people use is to break the data across different systems:
• Relational data goes to the RDBMS
• Embeddings go to a vector database
• JSON documents go to a NoSQL database
Trust me, this is a nightmare.
You don't want to synchronize updates and coordinate failures across all these systems.
The solution: "Converged Databases".
Here is how a converged database works:
1. You can save related changes in a single transaction. Every change either succeeds or fails.
2. Your queries can combine relational data, JSON documents, and vectors.
3. All changes across your data stay in sync at all times. You don’t need to wait for them to catch up.
4. Your permissions work regardless of how you search the data and the fields you retrieve.
5. You can work with different views of the same data. For example, you can return customer data as a JSON document or relational data.
Imagine you are building an agent to manage and support tickets. For any given action, this agent would need similarity search, current ticket status, customer information, and permission checks.
With a converged database, your agent can combine all those requirements into a single query.
That means faster queries, fewer synchronization pipelines, and less coordination in your code.
Here is a really good article about converged databases:
fandf.co/4rj8d3F
Thanks to the Oracle team for partnering with me on this post.
V retweeted
1/3 Conscious AI and Biological Naturalism. A veeery loooong time in the making, but I'm happy to say that the full collection is now out in @BBSJournal 🔥 I deeply thank all commentators - of fifty commentaries! - for their wise, broad, and deep opinions on this critical topic. I also thank them for their saintly patience. 🙏🏽
I remain highly skeptical about the prospects for conscious AI (for silicon digital systems), but I've learned an enormous amount from the privilege of engaging with these commentaries. Hands down one of the most rewarding experiences of my professional life.
My hope is that - whether you agree with me or not - having such a diversity of views collected in one place will serve a useful resource for discussions about consciousness and AI.
The original target article is available here: cambridge.org/core/journals/…
My response "The stuff matters: consciousness, computation, and biology" was published just now, and is here: cambridge.org/core/journals/…
And the set of 50 commentaries are collected here: cambridge.org/core/journals/…
Unfortunately these are not open access. I will try to remedy that, at least for the target & response.
FWIW there's a more accessible version of my view on the topic here in @NoemaMag noemamag.com/the-mythology-o… and also a short @TEDTalks from earlier this year ted.com/talks/anil_seth_why_…
V retweeted
Researchers at Oxford argue that LLMs can't invent anything.
It's impossible mathematically.
The paper is called "Theory Is All You Need."
Teppo Felin and Matthias Holweg take the famous "Attention Is All You Need" title and flip it. Their argument is that AI predicts from the past, while humans reason forward into the future, and those are two different kinds of thinking.
Start with the numbers. The authors estimate a large language model trains on roughly 13 trillion tokens. A human reading at 150 words a minute would need about 164,000 years to get through that. A child hears around 20,000 words a day and roughly 36.5 million words in their first five years. It's the same task with wildly different data, and the child still ends up with language that goes far beyond anything they heard.
Their point is that the model learns which words tend to follow other words. It becomes a mirror of what people have already written. It doesn't build a theory of how the world works, so it can't step outside its training data.
The paper's sharpest thought experiment makes this painful. Imagine an LLM trained in 1633 on every scientific text ever written up to that point. Ask it about Galileo and heliocentrism. Thousands of years of geocentric texts would swamp Galileo's ideas, so the model would tell you he's wrong. It would also rate Tycho Brahe's astrology as more credible than the idea that the Earth moves, because more people had written about astrology.
Then there's flight. In 1888 the scientist Joseph LeConte looked at bird data, noted that no bird above 50 pounds could fly, and concluded humans couldn't either. Lord Kelvin, then president of the Royal Society, said he had not the smallest molecule of faith in aerial navigation.
The New York Times estimated in 1903 that flight was one to ten million years away.
Nine weeks later the Wright brothers flew.
The Wrights didn't have better data. They had a theory. They broke flight into three problems, lift, propulsion, and steering, built their own wind tunnels, and generated the data that didn't exist yet.
Wilbur wrote in 1900 that he had been "afflicted with the belief that flight is possible to man."
Every prediction machine on Earth would have told him no.
The authors call this the data belief asymmetry. Every real breakthrough starts with someone believing something the existing data says is wrong. A system trained to minimize surprise can't do that by design.
They're not anti AI. They say AI will win at routine, repetitive decisions that extrapolate from the past, which is most decisions. They're just pushing back on the idea that you should replace humans with algorithms whenever possible, which is a direct quote from Kahneman.
I use these models every day and this matches what I see. The new stuff comes from the human at the keyboard who decides the data is wrong.
LLMs don't think, you do!
Microsoft is making moves again.
A quiet little Python tool just shot to the top of GitHub’s trending charts.
100,000+ stars.
It’s called MarkItDown.
And it does something deceptively simple:
It turns almost any file into clean Markdown.
PDFs. Word docs. PowerPoints. Excel files. Images.
Drop a file in. Get structured Markdown out.
Sounds small.
It’s not.
Because one of the biggest bottlenecks in AI workflows — especially RAG systems — is getting messy, real-world documents into a format models can actually use.
And real-world documents are brutal.
PDFs are chaotic.
Word docs are full of hidden formatting junk.
PowerPoints are messy and often image-heavy.
Spreadsheets can be a nightmare to parse cleanly.
That’s where this gets interesting.
MarkItDown strips away the friction and gives you something LLM pipelines can actually work with.
In other words: less preprocessing, less pain, faster AI implementation.
Even better, this isn’t some random side project.
It’s an official Microsoft open-source tool.
Free. Commercially usable. Practical.
I tested it on a 200-page PDF.
A few seconds later, I had Markdown that was shockingly clean.
And that’s what big tech does at its best:
They take an annoying, universal problem that everyone has been duct-taping together…
and turn it into a simple standard.
That’s why this matters.
It’s not just a file conversion tool.
It’s infrastructure for the next wave of AI applications.
Get it here: github.com/microsoft/markitd…
===
🚨 Want to learn how to build + ship AI and Data Science projects (that businesses actually want in 2026)?
I am hosting a free workshop to help you get started with AI + DS projects in Python.
Register here (500 seats): learn.business-science.io/ai…
V retweeted
Spotify just published the internal setup their engineers use with Claude Code, the one that cut token usage by 90 percent. Here is how it works.
The observation behind it: most of what a coding assistant does is not thinking. It opens five files to answer a question about one of them. It writes a test that copies the pattern of the twenty tests sitting next to it. Enormous amounts of work, almost no judgment, and all of it billed at top rates.
So they added two cheap assistants. One opens the files and hands back a short summary. The other writes the repetitive code from an example and saves it straight to disk. The expensive model never sees any of it.
The clever part is how they made it stick. First the rules were written down as instructions, and the model ignored them. Now anything over 350 lines gets stopped before it opens and sent to the cheap one instead. Written rules are a suggestion. A block is not.
Two things stayed expensive. Edits still need the real file. And the cheap worker missed a bug the expensive one caught in seconds.
V retweeted
A thread of some new work that’s appeared since I was last on this platform a couple of years ago!
⬇️🧵 🧠
1) A lecture for Michael Levin’s symposium on Platonic spaces in biology.
youtu.be/pqDnfNUlvRo
V retweeted
No country for old linguists: LLM-brain alignment underdetermines neural computation
arxiv.org/abs/2609.03160
V retweeted
Paper: arxiv.org/abs/2608.29530
We consider a variety of neural networks that perform seemingly-symbolic tasks, from small-scale models trained on simple list-manipulation tasks to LLMs performing tasks in math, logic, coding, and language.
2/n
V retweeted
Introducing TimesFM-3, a state-of-the-art time series foundation model that enables accurate multivariate time series forecasting in a single forward pass, significantly outperforming other forecasting models across major benchmarks.
More on the blog →goo.gle/4x5WGpD
































