CCC retweeted
Exactly this. We need progressive disclosure for AI responses.
I keep having this strange experience.
I'll open a model response and just... stare at it for a moment.
Not because I don't understand the individual words.
Because every paragraph is carrying so much context that my brain instinctively starts searching for a foothold. A familiar analogy. A single thread to pull. Some place to begin unraveling the tapestry.
The strange part is that this is my own project.
I know the architecture. I know the history. I know why every decision was made.
And yet, more and more often, my next prompt is simply:
"Explain that more simply."
A year ago I was asking the models for maximum depth. I wanted the answer a room full of PhDs would give each other.
Now I find myself asking for something almost opposite. Not less intelligence, just less compression. Fewer ideas per paragraph. More places for a human mind to come up for air.
The models aren't inventing a new language.
They're speaking perfectly recognizable English.
It's just that every sentence has become densely connected to every other sentence. Each paragraph feels like a compressed graph of ideas that my brain has to slowly expand back into something I can hold in working memory.
Sometimes I can't tell if the models are accelerating, or if I've simply found the bandwidth limit of my own cognition.
I wonder what this feels like a year from now.
Maybe the scarce resource isn't intelligence.
Maybe it's human comprehension.
my lord, i am having an absurd amount of fun playing with kimi.
it has almost no visible guardrails (no copyrights or anything). it doesn’t constantly push back, tell me it can’t help, or interrupt the flow with refusals.
it just does it. even some crazy stuff.
whether you agree with that philosophy or not, it is easily the least constrained frontier class model that’s broadly accessible right now.
using it feels genuinely god damn different. WOW.
Damn it they just upgraded models close to nih grant deadline again. The last good writer is gone. I used to communicate with claude and ask it to write and dispatch gpt for code and theory. Now we have two autistic model optimized just to code nitter.gq/Simeon_Cps/status/2061…
Opus 4.8 Max is as autistic as it gets.
Ask a simple mildly underspecified query and read its chain of thoughts.
It’ll make you feel sorry to have asked that question.
2
155
CCC retweeted
Replying to @charliermarsh
Sometimes they're a good reason to work on something. When people say a market is "crowded," what that often means is that there's a real problem and none of the solutions are good enough yet.
CCC retweeted
I think we have entered the golden era of lone researchers who can carry out the entire work themselves.
I bet many professors feel this way but choose not to say it publicly.
I was talking to a CS professor yesterday and he told me he's so relieved ⛱️ now that his PhD students have left for their summer internships.🌞. He finally gets to do interesting research himself again. It wasn't a complaint. Just something he'd been sitting with.
The old PhD bargain was pretty clean: professors had ideas, students had time, execution was the bridge. You did the work, and somewhere along the way, taste rubbed off.
That bridge is mostly gone now. A senior researcher with taste and a research agents ships faster than the same researcher plus a junior student. Explaining 🎙️ an idea to someone who doesn't yet have taste costs more than just building it. (the reason professor still needs students is because the research agent 🤖 is not yet capable enough)
Nobody wants to say this out loud
Professors keep mentoring because the system 🏫 asks them to, not because it's the highest-leverage thing they could be doing with their week.
The thing that still matters —> taste <— was never really taught. It was supposed to leak out of the execution. Now there's no execution to leak from.
CCC retweeted
I was talking to a CS professor yesterday and he told me he's so relieved ⛱️ now that his PhD students have left for their summer internships.🌞. He finally gets to do interesting research himself again. It wasn't a complaint. Just something he'd been sitting with.
The old PhD bargain was pretty clean: professors had ideas, students had time, execution was the bridge. You did the work, and somewhere along the way, taste rubbed off.
That bridge is mostly gone now. A senior researcher with taste and a research agents ships faster than the same researcher plus a junior student. Explaining 🎙️ an idea to someone who doesn't yet have taste costs more than just building it. (the reason professor still needs students is because the research agent 🤖 is not yet capable enough)
Nobody wants to say this out loud
Professors keep mentoring because the system 🏫 asks them to, not because it's the highest-leverage thing they could be doing with their week.
The thing that still matters —> taste <— was never really taught. It was supposed to leak out of the execution. Now there's no execution to leak from.
CCC retweeted
Hamming's talk is so important that I reproduced it on my site. It's one of the only things on my site written by someone else.
paulgraham.com/hamming.html
A mathematician who shared an office with Claude Shannon at Bell Labs gave one lecture in 1986 that explains why some people win Nobel Prizes and other equally smart people spend their whole lives doing forgettable work.
His name was Richard Hamming. He won the Turing Award. He invented error-correcting codes that made modern computing possible. And he spent 30 years at Bell Labs sitting in a cafeteria at lunch watching which scientists became legendary and which ones faded into nothing.
In March 1986, he walked into a Bellcore auditorium in front of 200 researchers and told them exactly what he had seen.
Here's the framework that has been quoted by every serious scientist for the last 40 years.
His opening line landed like a punch. He said most scientists he worked with at Bell Labs were just as smart as the Nobel Prize winners. Just as hardworking. Just as credentialed. And yet at the end of a 40-year career, one group had changed entire fields and the other group was forgotten by the time they retired.
He wanted to know what the difference actually was. And he said it wasn't luck. It wasn't IQ. It was a specific set of habits that almost nobody is willing to follow.
The first habit was the one that hurts the most to hear. He said most scientists deliberately avoid the most important problem in their field because the odds of failure are too high. They pick a safe adjacent problem, solve it cleanly, publish it, and move on. And because they never swing at the hard problem, they never hit it. He said if you do not work on an important problem, it is unlikely you will do important work. That is not a motivational line. That is a logical one.
The second habit was about doors. Literal doors. He noticed that the scientists at Bell Labs who kept their office doors closed got more done in the short term because they had no interruptions. But the scientists who kept their doors open got more done over a career. The open-door scientists were interrupted constantly. They also absorbed every new idea passing through the hallway. Ten years in, they were working on problems the closed-door scientists did not even know existed.
The third habit was inversion. When Bell Labs refused to give him the team of programmers he wanted, Hamming sat with the rejection for weeks. Then he flipped the question. Instead of asking for programmers to write the programs, he asked why machines could not write the programs themselves. That single inversion pushed him into the frontier of computer science. He said the pattern repeats everywhere. What looks like a defect, if you flip it correctly, becomes the exact thing that pushes you ahead of everyone else.
The fourth habit was the one that hit me the hardest. He said knowledge and productivity compound like interest. Someone who works 10 percent harder than you does not produce 10 percent more over a career. They produce twice as much. The gap doesn't add. It multiplies. And it compounds silently for years before anyone notices.
He finished the lecture with a line I have never been able to shake.
He said Pasteur's famous quote is right. Luck favors the prepared mind. But he meant it literally. You don't hope for luck. You engineer the conditions where luck can land on you. Open doors. Important problems. Inverted questions. Compounded hours. Those are not traits. Those are choices you make every single day.
The transcript has been sitting on the University of Virginia's computer science website for almost 30 years. The video is free on YouTube. Stripe Press reprinted the full lectures as a book in 2020 and Bret Victor wrote the foreword.
Hamming died in 1998. He gave his final lecture a few weeks before. He was 82.
The lecture that explains why some careers become legendary and others disappear is still free. Most people who could benefit from it will never open it.
CCC retweeted
In SF, never ask why your friend is late to lunch or dinner.
There’s only one reason:
they were fighting for their life writing a prompt so Claude Code/Codex could run for 1+ hour without them.
CCC retweeted
“Reading after a certain age diverts the mind too much from its creative pursuits. Any man who reads too much and uses his own brain too little falls into lazy habits of thinking, just as the man who spends too much time in the theater is tempted to be content with living vicariously instead of living his own life.” — Albert Einstein
CCC retweeted
Everybody I know using AI is working more hours not less.
Powerful new Harvard Business Review study.
"AI does not reduce work. It intensifies it. "
A 8-month field study at a US tech company with about 200 employees found that AI use did not shrink work, it intensified it, and made employees busier.
Task expansion happened because AI filled in gaps in knowledge, so people started doing work that used to belong to other roles or would have been outsourced or deferred.
That shift created extra coordination and review work for specialists, including fixing AI-assisted drafts and coaching colleagues whose work was only partly correct or complete.
Boundaries blurred because starting became as easy as writing a prompt, so work slipped into lunch, meetings, and the minutes right before stepping away.
Multitasking rose because people ran multiple AI threads at once and kept checking outputs, which increased attention switching and mental load.
Over time, this faster rhythm raised expectations for speed through what became visible and normal, even without explicit pressure from managers.
CCC retweeted
Universities are still policing AI like it's a plagiarism problem.
Meanwhile, the gap is widening.
The researchers who figure out AI isn't for writing papers, know it's for accelerating research, filling knowledge gaps, handling the grunt work that blocks breakthrough thinking. They're already pulling ahead.
By the time your institution finalizes its "AI detection policy," those researchers will have published twice as much, explored ideas you're still stuck researching manually, and freed up mental space for the work that actually matters.
You can spend your energy hiding AI use, or you can spend it mastering AI as leverage.
One of those paths leads somewhere.
Code up fast with codex. Ask for human readable notebooks walking you through that code from claude. Codex can't do that. Claude is slow for the first.
GPT-5.2 is the BEST coding agent right now.
It does what you ask, and it works.
WHY?
1. I always had to correct Claude Code.
2. Gemini is trash. Switches languages and removes features.
3. Grok is confident but can’t write modern Swift. Too many compiler errors.
88
Have been sleeping 4 hr per night over the last month. Finished 10 papers. Struggling to go to bed and stay sleep. Every student and collaborator seems slow and all meetings are boring. Just want to go talk to my agents.
gpt is ruining my work life balance, its like having a phd student that never stops working, so then I never stop. I keep wanting to stay up for another 45 min to see if it correctly did my proof sketch or fixed the issue I found in previous message. Bedtime getting pushed later and later and weekends disappearing to prompting gpt.
1
62























