NeuralVector retweeted
The people building AI earnestly believe that it could kill us all by the end of the decade. This is not a marketing stunt. If anything, many executives and senior researchers will couch their phrasing in the press to sound sensible - but I hear the same people express fear privately. No other human activity poses this level of danger.
NeuralVector retweeted
Shaa guide ooo, just guide..
They call Jesus “son of David”
Because Joseph na Carpenter, pikin wey him suffer train ooo 💔😂
NeuralVector retweeted
Feminists are about to “F” around and find out what a world without men in their lives looks like.
NeuralVector retweeted
i genuinely hate building normal web projects,
i prefer building things that makes me question my sanity
NeuralVector retweeted
Before you watch this video, I want you to injest every word that comes out of the narrators mouth.
Don't lose focus or allow anyone to distract you.
Towards the end, she emphasised on two key things:
1. The feminine strength is cunning
2. Gynocentric indoctrination
Watch it
NeuralVector retweeted
“If the first man was white ….”
Minister Farrakhan ate and left no crumbs and I’m so here for it☕️ Class is in session!
NeuralVector retweeted
Kubernetes killed more startups than server crashes ever did
You don't have Spotify's scale. You have 8 engineers and a single server that's running fine
But you watched a KubeCon talk, and now you've got 23 YAML files, a Helm chart nobody fully understands, and engineers debugging pod evictions instead of buildinga product
Your "cloud-native infrastructure" is just a cloud bill with extra complexity
A $50/month VM can handle millions of requests. Your startup will run out of money debugging networking issues long before you need horizontal pod autoscaling
The best infrastructure decision is often the simplest one
NeuralVector retweeted
R.I.P few-shot prompting.
Meta AI researchers discovered a technique that makes LLMs 94% more accurate without any examples.
It's called "Chain-of-Verification" (CoVe) and it completely destroys everything we thought we knew about prompting.
Here's the breakthrough (and why this changes everything): 👇
NeuralVector retweeted
Build fully offline mobile assistants with FunctionGemma 270M. This demo parses natural language commands like “Create a calendar event for lunch tomorrow” or “Add to contacts” to execute OS actions directly on-device.
NeuralVector retweeted
ICYMI DeepSeek has just unveiled an OCR monster 🤯
DeepSeek-OCR is a 3B-parameter model that redefines document intelligence. It reaches 97% character-level accuracy with 10× input compression, preserving every detail.
Most OCR systems require over 6,000 tokens per page.
DeepSeek-OCR achieves the same with about 100 tokens.
No fidelity loss.
Adaptive modes:
✓ Tiny – simple layouts (≈64 tokens)
✓ Small – standard reports (≈100 tokens)
✓ Database – structured or multi-column docs (≈256 tokens)
✓ Gundam – high-complexity pages (n×100 + 256 tokens)
It scales effortlessly: 200K pages/day on a single NVIDIA A100 GPU.
Its dual-stage design combines a vision encoder for optical compression with a Mixture-of-Experts decoder for structured reconstruction. The outcome is near-perfect precision and zero information loss.
In practice:
➤ 10× lower token costs
➤ Runs on standard hardware
➤ Outputs clean HTML, SMILES, or JSON
While traditional OCRs focus on raw pixel-to-text conversion, DeepSeek-OCR just introduces intelligent semantic parsing 🔥
Open source and free to use.
Repo in 🧵↓
NeuralVector retweeted
This paper from MIT puts actual numbers behind a feeling many people working with LLMs already have: most model failures are not knowledge failures, they’re first-draft failures.
The paper studies Recursive Language Models (RLMs) and asks a very specific question:
What happens if you let the same model revise its own output multiple times instead of scaling parameters?
The answer is surprisingly concrete.
Across reasoning-heavy benchmarks, the authors show that recursion consistently improves accuracy with no change in model size.
On multi-step reasoning tasks, adding just 2–4 recursive passes improves correctness by 10–25%, depending on task complexity. On longer planning problems, error rates drop even more sharply, because early logical mistakes get corrected in later passes instead of propagating forward.
One figure in the paper makes this especially clear.
They plot task accuracy vs. recursion depth.
The curve is steep at first:
• Pass 1 → baseline performance
• Pass 2 → large jump in correctness
• Pass 3–4 → diminishing but still meaningful gains
After ~4 iterations, returns taper off, which suggests something important: most reasoning failures happen early, and a small amount of structured revision fixes a large fraction of them.
There’s also a cost comparison that’s hard to ignore.
The authors compare:
• A larger non-recursive model
• A smaller recursive model using multiple passes
The recursive model reaches comparable or better accuracy while using fewer parameters and fewer total tokens in the final answer. Even though recursion adds compute internally, the output length shrinks because later passes compress and clean up earlier drafts.
In plain terms: the model thinks more, but talks less.
Another quantitative result I found fascinating is hallucination reduction.
The paper measures factual consistency across iterations and finds that later recursive passes explicitly remove unsupported claims introduced in earlier drafts. The probability of a hallucinated statement surviving to the final output drops significantly after the second pass, because the model is now evaluating its own content instead of blindly extending it.
This directly challenges the “long chain-of-thought = better reasoning” assumption.
The data suggests the opposite.
Better reasoning comes from iterative self-correction, not from dumping more intermediate tokens. The recursion acts like an internal verifier that gradually aligns the output with constraints imposed by the task.
There’s also a subtle systems insight hidden in the math.
If accuracy improves roughly logarithmically with recursion depth but model size improves accuracy sublinearly with parameter count, then recursion is simply a more efficient lever. You get more reasoning per unit of compute by looping than by scaling.
That’s a big deal for deployment.
Instead of asking:
“How big can we make the model?”
This paper asks:
“How many chances does the model get to be wrong before we trust it?”
The broader implication is hard to miss.
We’ve been benchmarking models on their first answer.
But intelligence doesn’t live in the first answer.
It lives in revision curves, error decay rates, and how quickly a system converges toward correctness when allowed to reflect.
This paper doesn’t just propose a technique.
It quietly suggests we’ve been measuring the wrong thing all along.
NeuralVector retweeted
DeepSeek just fixed one of AI's oldest problems.
(using a 60-year-old algorithm)
Here's the story:
When deep learning took off, researchers hit a wall. You can't just stack layers endlessly. Signals either explode or vanish. Training deep networks was nearly impossible.
ResNets solved this in 2016 with residual connections:
output = input + what the layer learned
That "+" creates a direct highway for information. This is why we can now train networks with hundreds of layers.
Recently, researchers asked: what if we had multiple highways instead of one?
Hyper-Connections (HC) expanded that single lane into 4 parallel lanes with learnable matrices that mix information between streams.
The performance gains were real. But there was a problem:
Those mixing matrices compound across layers. A tiny 5% amplification per layer becomes 18x after 60 layers. The paper measured amplification reaching 3000x. Training collapses.
The usual fixes? Gradient clipping. Careful initialization. Hoping things work out.
These are hacks. And hacks don't scale.
DeepSeek went back to first principles. What mathematical constraint would guarantee stability?
The answer was sitting in a 1967 paper: the Sinkhorn-Knopp algorithm.
It forces mixing matrices to be "doubly stochastic," where rows and columns each sum to 1.
The results:
- 3000x instability reduced to 1.6x
- Stability guaranteed by math, not luck
- Only 6.7% additional training overhead
No hacks. Just math.
I've shared link to the paper in the next tweet.
NeuralVector retweeted
I finally understand the difference between LLMs, RAG, and AI Agents...
After two years of building production AI systems, I realized most people are treating them like competing tools when they’re actually three layers of the same intelligence stack.
1. The LLM is the brain.
It’s the reasoning engine. It understands language, writes, explains, and synthesizes ideas better than any system before it. But it’s frozen in time. GPT-4, for example, knows nothing past its last training update. Ask it about yesterday’s events and it’ll confidently make something up. LLMs can think, but they’re disconnected from the present.
2. RAG is the memory.
It’s what connects that frozen brain to live knowledge. Instead of retraining the model, RAG retrieves fresh information from your company’s data, APIs, or the web and feeds it to the LLM as context. Now the model reasons over real, up-to-date facts rather than outdated patterns. The best part? You can trace exactly which documents shaped each answer. It’s the difference between guessing and knowing.
3. AI Agents are the decision-makers.
They wrap a control loop around the system. The agent perceives goals, plans actions, executes tasks, and reflects on the outcome. It’s not just answering a question—it’s doing the work. Think of an AI that researches, drafts a report, sends an email, and iterates on feedback, all autonomously. That’s what an agent does.
Most “AI” demos stop at the LLM stage. Real production systems combine all three: the LLM for reasoning, RAG for accuracy, and the Agent for autonomy.
Use LLMs for pure thinking tasks writing, summarizing, explaining.
Add RAG when precision and truth matter like referencing internal documents or specialized data.
Deploy Agents when you need end-to-end action systems that decide and operate without manual input.
The future of AI isn’t one layer beating the others. It’s about architecting all three together.
LLMs think.
RAG remembers.
Agents act.
That’s the real intelligence stack.
NeuralVector retweeted
The longer you spend in tech, the stronger the urge to buy a farm and never touch a computer again in your life.
NeuralVector retweeted
Can LLMs learn to act like real doctors instead of just summarizing cases?
DiagAgent does exactly that — trained with reinforcement learning in a simulated clinical world (DiagGym), it learns to plan tests, reason across turns, and make final diagnoses.
Outperforming GPT-4o, DeepSeek-v3, and others by large margins, it shows that interactive training unlocks truly adaptive diagnostic intelligence.
Evolving Diagnostic Agents in a Virtual Clinical Environment
SJTU, SAIL, and others
Paper: arxiv.org/abs/2510.24654
Code: github.com/MAGIC-AI4Med/Diag…
Our report: mp.weixin.qq.com/s/byVmM-0Ht…
📬 #PapersAccepted by Jiqizhixin





























