Yeah this just reads like rehashed applied math research vs foundational math research, and i think you overestimate the abilities of humans to immediately know the point of fundamental research, when time and again we have realized its application only after decades. Its a lazy argument, is all.
A 27-year-old pointed Claude Code at 4,000 Obsidian notes and woke up to an employee he never hired.
6 years of notes. Ideas, half-finished essays, 212 book summaries all rotting in a folder he stopped opening in 2024.
Then he noticed something obvious that almost nobody uses.
Obsidian is just markdown files, and Claude Code lives in the terminal which means his entire second brain is one cd command away from an AI that can read all of it.
So he ran it once, overnight.
By 7 AM the agent had crawled every note, linked 340 orphan ideas back into the graph, flagged 18 contradictions between things he believed in 2021 and things he wrote in 2025, and drafted 6 essays from threads he forgot existed.
Now the loop runs every night while he sleeps.
New note goes in messy wakes up tagged, linked, connected to 3 older notes he'd never have found himself. His daily note greets him with what he was thinking exactly 1 year ago and why he was wrong.
Cost of the setup: 1 folder path and a 400-word CLAUDE.md file.
No plugins, no Notion AI subscription, no $30/month "second brain" course.
People spent a decade building vaults that just sit there.
He built one that thinks back.
Ever since i have been using LLMs for work, 99% of menial work has been automated and I have been exclusively working on only hard problems. It has encouraged me to work more because i find meaning in working on hard problems. I go home a lot more tired now than 6 months ago because I do alot more in a day than I could have done earlier.
Self-evolving: AttnRes Kernel Optimization
Given FLA Triton AttnRes at production scale (96 layers, 8192-dim model, 8192 tokens), the goal was to maximize training-side speed without changing numerics.
Over 15 hours of nonstop iteration, K3 designed a novel two-phase kernel algorithm, fused kernels while preserving numerics, and reduced forward+backward time from 283.6 ms to 114.4 ms.
K3 and Fable-5 (with potential fallback) reached similar performance, but K3 improved faster per iteration.
Nooooo, you dont understand you have to do a humanities degree and have to spend 5 years typing word documents for a living to talk policy with us....wait are you saying what your model is telling you to say!?
Man it kinda feels like we are bottle necked by our memories and our abilities to read stuff slowly. I wish to remember alot of stuff and read a things very quickly.
I like Zig too, but I’m not convinced by the argument that TigerBeetle proves memory management is not hard in Zig, and that projects struggling with it simply have a “skill issue.”
TigerBeetle’s memory model is fundamentally different from that of a typical application. Many real-world workloads are difficult, or even impossible, to estimate in advance. For something like the Bun bundler(or Rspack), which has to process arbitrary user code, I don’t see how you could reliably predict an upper bound on memory usage ahead of time.
So we may need a better example(ghostty maybe a better one) of how memory can be managed well in a large, general-purpose system—especially in complex scenarios involving FFI, like Bun. TigerBeetle is an impressive project, but it is not a representative case.