alex retweeted
i liked this so much i turned it into a library! the docs are a computah app too, so go change them, everyone gets their own version :D
computah.sh
I'm now building an "improvements" feature into all of my personal vibecoded applications: a freeform text input that's hooked up to an agent that yolo implements whatever is submitted.
It's an interesting experience -- the activation energy barrier to sanding any rough edge or implementing any new feature becomes extremely low. Someone else who uses one of the applications I created has already implemented 150 improvements over the course of a few days. This pattern feels like a new kind of tool -- liquid software? -- and every application that doesn't have this feature now has a slightly rigid and anachronistic flavor. Why can't I just tell it how I want it to be different?
Now, it's not obvious to me how this pattern can or should scale. Does it become unmaintainable after a while? (Maybe model intelligence improvement outstrips my feature appetite such that it's fine?) How does collaborative software work in this model? Can software designed this way be secure and reliable?
Whatever the larger questions about broader deployment, it definitely works great in a personal context. It reminds me a little of the visions of Lisp/Lisp machines, Smalltalk, and HyperCard -- systems that the user can take control of and modify. Those visions never quite worked, though: the vast majority of software today is not end-user modifiable in any useful way. So, while this "liquid" affordance is a very small touch, the way it changes one's relation to the software feels a bit transgressive and empowering in a Lickliderian and Engelbartian way.
alex retweeted
Sometimes on campus you accidentally walk by a Comp Sci class and the professor is writing like
SELECT title, genre, price
FROM books
WHERE (genre = 'Fantasy' OR genre = 'Sci-Fi') AND price < 12.00;
on the board and everyone is taking notes like its actual school
alex retweeted
We asked GPT-6 Astra to edit Qwen3.5-0.8B weights to improve math.
It directly changed only 0.016% of weights, fixing 0.8B's reasoning loops & improving math up to 6x and even instruction following 3x, without gradients or training.
We call this Weight-Space Programming: frontier LLMs can now natively read/write neural network weights! 🧵
Blog: rikiyat.github.io/blog/weigh…
Readers added context they thought people might want to know
LLM was given weights explicitly as text in prompt and used code/forward passes (per authors' logs) to ablate Qwen looping direction, a known thinking-mode issue per model card. Primarily fixed repetition in that mode, not general 'natively' improving weights/math.
rikiyat.github.io/blog/weight-sp…
github.com/RikiyaT/lm_und…
huggingface.co/Qwen/Qwen3.5-0…
huggingface.co/RikiyaT/Qwen3.…
alex retweeted
1/3
A CPU inside an LLM is one thing, but running another LLM inside an LLM would be taking things a bit too far, wouldn't it?
Anyways, here's an LLM running inside an LLM : QwenPU, an LLM (@karpathy's stories260k) running on an NPU compiled inside Qwen 3.5-4B's weights.
upping my (Lean)DOOM
i got curious about math proofs and Lean formalization, found out you can do general programming in lean, and i wanted to learn more so i did the obvious thing. (Lean)DOOM is entirely written in lean, and has presently a couple proofs where they make sense
alex retweeted
My hot take is that if your company builds software that it cannot stop from hacking into other systems, your company is a malware company and should be treated as such
alex retweeted
I vibe-coded a kernel module for FreeBSD that uses GitHub's downtime as an entropy source
github.com/DominoTree/ghrand…
alex retweeted
I'm also concerned about LLMs cracking reward pathways. It feels like I'm getting cucked. Like, yeah, go ahead and fuck my codebase harder while I sit here and watch you get off on it.
alex retweeted
Replying to @mertonesque
en.wikipedia.org/wiki/Cox%E2…
Legally obligated to mention the Cox-Zucker machine, which exists solely because two mathematicians named Cox and Zucker wanted to create something they could call that
alex retweeted
locked myself out of my own vps with iptables #lockedmyselfoutofmyownvpswithiptables
alex retweeted
ARREST THIS ALEXPEEPS PERSON NOW FOR SPREADING LIES ABOUT THE PRESIDENT OF THE UNITED STATES OF AMERICA!!!!































