Will Rice

1.2K posts

Will Rice banner
Will Rice

Will Rice

@_Will_Rice

ML Engineer working on generative models in #Speech and #NLP. Focused on Text-to-Speech (TTS) and speaker generation.

United States Katılım Ekim 2016
233 Takip Edilen239 Takipçiler
Weights & Biases
Weights & Biases@wandb·
@_Will_Rice Could you tell us what you mean? It should be apart of the free plan. Feel free to dm us a screenshot!
English
1
0
0
81
Will Rice
Will Rice@_Will_Rice·
Is making a team and paying for a seat the only way to get notifications for @wandb anymore?
English
1
0
1
112
Will Rice
Will Rice@_Will_Rice·
@karpathy Mostly agree, except I’ve totally had Claude code suggest to add ignore comments to mypy errors after tying to fix it. So I think it does get stuck and give up. The difference is you can just say “don’t reference my other chats” and it will try again.
English
0
0
0
576
Andrej Karpathy
Andrej Karpathy@karpathy·
A few random notes from claude coding quite a bit last few weeks. Coding workflow. Given the latest lift in LLM coding capability, like many others I rapidly went from about 80% manual+autocomplete coding and 20% agents in November to 80% agent coding and 20% edits+touchups in December. i.e. I really am mostly programming in English now, a bit sheepishly telling the LLM what code to write... in words. It hurts the ego a bit but the power to operate over software in large "code actions" is just too net useful, especially once you adapt to it, configure it, learn to use it, and wrap your head around what it can and cannot do. This is easily the biggest change to my basic coding workflow in ~2 decades of programming and it happened over the course of a few weeks. I'd expect something similar to be happening to well into double digit percent of engineers out there, while the awareness of it in the general population feels well into low single digit percent. IDEs/agent swarms/fallability. Both the "no need for IDE anymore" hype and the "agent swarm" hype is imo too much for right now. The models definitely still make mistakes and if you have any code you actually care about I would watch them like a hawk, in a nice large IDE on the side. The mistakes have changed a lot - they are not simple syntax errors anymore, they are subtle conceptual errors that a slightly sloppy, hasty junior dev might do. The most common category is that the models make wrong assumptions on your behalf and just run along with them without checking. They also don't manage their confusion, they don't seek clarifications, they don't surface inconsistencies, they don't present tradeoffs, they don't push back when they should, and they are still a little too sycophantic. Things get better in plan mode, but there is some need for a lightweight inline plan mode. They also really like to overcomplicate code and APIs, they bloat abstractions, they don't clean up dead code after themselves, etc. They will implement an inefficient, bloated, brittle construction over 1000 lines of code and it's up to you to be like "umm couldn't you just do this instead?" and they will be like "of course!" and immediately cut it down to 100 lines. They still sometimes change/remove comments and code they don't like or don't sufficiently understand as side effects, even if it is orthogonal to the task at hand. All of this happens despite a few simple attempts to fix it via instructions in CLAUDE . md. Despite all these issues, it is still a net huge improvement and it's very difficult to imagine going back to manual coding. TLDR everyone has their developing flow, my current is a small few CC sessions on the left in ghostty windows/tabs and an IDE on the right for viewing the code + manual edits. Tenacity. It's so interesting to watch an agent relentlessly work at something. They never get tired, they never get demoralized, they just keep going and trying things where a person would have given up long ago to fight another day. It's a "feel the AGI" moment to watch it struggle with something for a long time just to come out victorious 30 minutes later. You realize that stamina is a core bottleneck to work and that with LLMs in hand it has been dramatically increased. Speedups. It's not clear how to measure the "speedup" of LLM assistance. Certainly I feel net way faster at what I was going to do, but the main effect is that I do a lot more than I was going to do because 1) I can code up all kinds of things that just wouldn't have been worth coding before and 2) I can approach code that I couldn't work on before because of knowledge/skill issue. So certainly it's speedup, but it's possibly a lot more an expansion. Leverage. LLMs are exceptionally good at looping until they meet specific goals and this is where most of the "feel the AGI" magic is to be found. Don't tell it what to do, give it success criteria and watch it go. Get it to write tests first and then pass them. Put it in the loop with a browser MCP. Write the naive algorithm that is very likely correct first, then ask it to optimize it while preserving correctness. Change your approach from imperative to declarative to get the agents looping longer and gain leverage. Fun. I didn't anticipate that with agents programming feels *more* fun because a lot of the fill in the blanks drudgery is removed and what remains is the creative part. I also feel less blocked/stuck (which is not fun) and I experience a lot more courage because there's almost always a way to work hand in hand with it to make some positive progress. I have seen the opposite sentiment from other people too; LLM coding will split up engineers based on those who primarily liked coding and those who primarily liked building. Atrophy. I've already noticed that I am slowly starting to atrophy my ability to write code manually. Generation (writing code) and discrimination (reading code) are different capabilities in the brain. Largely due to all the little mostly syntactic details involved in programming, you can review code just fine even if you struggle to write it. Slopacolypse. I am bracing for 2026 as the year of the slopacolypse across all of github, substack, arxiv, X/instagram, and generally all digital media. We're also going to see a lot more AI hype productivity theater (is that even possible?), on the side of actual, real improvements. Questions. A few of the questions on my mind: - What happens to the "10X engineer" - the ratio of productivity between the mean and the max engineer? It's quite possible that this grows *a lot*. - Armed with LLMs, do generalists increasingly outperform specialists? LLMs are a lot better at fill in the blanks (the micro) than grand strategy (the macro). - What does LLM coding feel like in the future? Is it like playing StarCraft? Playing Factorio? Playing music? - How much of society is bottlenecked by digital knowledge work? TLDR Where does this leave us? LLM agent capabilities (Claude & Codex especially) have crossed some kind of threshold of coherence around December 2025 and caused a phase shift in software engineering and closely related. The intelligence part suddenly feels quite a bit ahead of all the rest of it - integrations (tools, knowledge), the necessity for new organizational workflows, processes, diffusion more generally. 2026 is going to be a high energy year as the industry metabolizes the new capability.
English
1.6K
5.5K
40K
7.7M
Will Rice
Will Rice@_Will_Rice·
@sedielem I put normalizing flow, but seeing flow-based in an abstract has changed over the years what I expect the paper to be about. Early in my career I would expect Real NVP, but now I would expect flow matching.
English
0
0
3
307
Sander Dieleman
Sander Dieleman@sedielem·
When I say "flow-based model", what do you think I am referring to?🤔 Seems like there might be some concept drift going on!
English
6
2
23
8.5K
Will Rice
Will Rice@_Will_Rice·
I find deep research from @OpenAI super useful. However, I would like to see improvement in the output format. I always want it to be in markdown but it leaves out information when asked to convert it to markdown. If anyone has luck with getting the full output in a markdown file, I would appreciate any tips.
English
0
0
0
63
Will Rice
Will Rice@_Will_Rice·
what do you do when you get rate limited by your AI therapist?
English
0
0
1
39
Will Rice
Will Rice@_Will_Rice·
So we tuning on the test set now?
English
0
0
1
30
Will Rice retweetledi
William
William@williamwelsh·
@thdxr we heard you like abstracting so we abstracted your abstraction to give you more abstraction 🤩
English
0
2
32
12.1K
Will Rice
Will Rice@_Will_Rice·
@timClicks If you look at the code for the paper there is a lot of triton cuda stuff
English
0
0
0
77
Tim McNamara
Tim McNamara@timClicks·
If this is accurate, then NVIDIA's grip on the tech industry has just vanished. Matrix matrix multiplication (MatMul) is notoriously computationally difficult, which is why it's offloaded to GPUs. If MatMul can be avoided, then it's not just leveling the playing field. It's creating new playing fields.
Rohan Paul@rohanpaul_ai

This is really a 'WOW' paper. 🤯 Claims that MatMul operations can be completely eliminated from LLMs while maintaining strong performance at billion-parameter scales and by utilizing an optimized kernel during inference, their model’s memory consumption can be reduced by more than 10× compared to unoptimized models. 🤯 'Scalable MatMul-free Language Modeling' Concludes that it is possible to create the first scalable MatMul-free LLM that achieves performance on par with state-of-the-art Transformers at billion-parameter scales. 📌 The proposed MatMul-free LLM replaces MatMul operations in dense layers with ternary accumulations using weights constrained to {-1, 0, +1}. This reduces computational cost and memory utilization while preserving network expressiveness. 📌 To remove MatMul from self-attention, the Gated Recurrent Unit (GRU) is optimized to rely solely on element-wise products, creating the MatMul-free Linear GRU (MLGRU) token mixer. The MLGRU simplifies the GRU by removing hidden-state related weights, enabling parallel computation, and replacing remaining weights with ternary matrices. 📌 For MatMul-free channel mixing, the Gated Linear Unit (GLU) is adapted to use BitLinear layers with ternary weights, eliminating expensive MatMuls while maintaining effectiveness in mixing information across channels. 📌 The paper introduces a hardware-efficient fused BitLinear layer that optimizes RMSNorm and BitLinear operations. By fusing these operations and utilizing shared memory, training speed improves by 25.6% and memory consumption reduces by 61% over an unoptimized baseline. 📌 Experimental results show that the MatMul-free LLM achieves competitive performance compared to Transformer++ baselines on downstream tasks, with the performance gap narrowing as model size increases. The scaling law projections suggest MatMul-free LLM can outperform Transformer++ in efficiency and potentially in loss when scaled up. 📌 A custom FPGA accelerator is built to exploit the lightweight operations of the MatMul-free LLM. The accelerator processes billion-parameter scale models at 13W beyond human-readable throughput, demonstrating the potential for brain-like efficiency in future lightweight LLMs.

English
109
433
4.6K
1.5M
Will Rice
Will Rice@_Will_Rice·
@JeremiahDJohns It’s interesting that some of these came from sources already on the internet that are obviously trolls/satire. That actually might be fixable if you could rank existing answers based on truthfulness.
English
1
0
1
2K
Jeremiah Johnson 🌐
Jeremiah Johnson 🌐@JeremiahDJohns·
Google's new AI search results are having quite the week. Here's a thread with some of my favorite answers:
Jeremiah Johnson 🌐 tweet media
English
2K
29.8K
360.6K
35.1M
Will Rice
Will Rice@_Will_Rice·
@jankosinski How do you know that it was accurately predicted?
English
1
0
0
223
Jan Kosinski
Jan Kosinski@jankosinski·
This is the end of the world as we know it, if this is reproducible! The new era of functional modeling has begun. I took a transcription factor with an unknown structure and folded it with its recognition sequence embedded in longer DNA. AlphaFold3 accurately positioned the transcription factor.
English
158
830
4.4K
1.9M
Will Rice retweetledi
Arun Rao
Arun Rao@sudoraohacker·
Hot take: ML researchers are underestimating how quickly recent scaling laws may flatten out - it’s quite likely what people see as an exponential function is a sigmoid, and the harsh reality of the physics of high energy costs and power plant construction restrict the expected benefits from pretraining of ever larger models.
English
5
9
36
7K
Will Rice
Will Rice@_Will_Rice·
tbh esembling would be too slow for the notebook submission
English
0
0
0
40