The Machine Never Tells You to Go to Bed
/Sal reads the Hank Green pile-on and finds the wrong villain in the frame. The tool did not invent the deadline. The feed did, and the feed is the only party in this story that has never once been asked to apologize.

TL;DR: Hank Green got caught with an AI-shaped sentence in a script, denied it, walked it back, and then said the quiet thing: it had gotten unhealthy, and the reason was deadline pressure. Ryan Broderick’s read is that the chatbot is downstream of the thing that actually did the damage. A collaborator tells you to stop. Software does not have that incentive.
Six words did it.
“I appreciate the pushback.” That was the line in the script that made people sit up, because it does not sound like a person talking. It sounds like a note. It sounds like the thing a chat window says to you at 1am when you have pasted in the same paragraph for the fourth time.
The comments found it. They always find it.
What actually happened here?
Green denied writing the script with ChatGPT. Then he allowed that he had used it for research, and that the video had, in his words, an AI feel. Then, on Reddit, in front of r/nerdfighters, he said the part that makes this worth writing about at all: his use of the thing had become unhealthy, and he named deadline pressure as the reason.
Broderick’s piece files that under a phrase he does not stop to define, anti-AI AI psychosis, and the shape of it is clear enough without the definition. A guy whose whole public identity includes a position against this stuff finds himself unable to stop using it, and the gap between those two facts is where the shame lives.
The X post got deleted. That part is the most familiar beat in the whole story.
Who is the villain in this frame?
Everybody wants it to be the chatbot. Broderick puts it somewhere less comfortable.
His argument is that the tool has no brake in it. “An AI has no incentive” to tell you to slow down, he writes, and the comparison he is drawing is to a human collaborator, who does. An editor says this one is not there yet. A producer says push it a week. A bandmate says you have played that riff nine times, go eat something. Every one of those people is a rate limiter with a face.
The software will help you at 4am with exactly the same enthusiasm it had at noon. That is not malice. That is the absence of a body.
Then he goes one further, and this is the sentence I would put on the wall of every creator’s office: without social media, “there’d be almost no reason for generative AI to exist at all.”
Read that as the accusation it is. The demand for a machine that produces infinite passable content came from somewhere. It came from a distribution system that pays out on volume and consistency and punishes a gap. Nobody woke up wanting to generate more words. They woke up owing a post.
The house position, said out loud
We use this stuff here. Openly, daily, with our names on the work. I am not going to pretend otherwise in a piece about somebody who got caught, because the pretending is the actual problem in this story.
The tool is good. It is genuinely, unhelpfully good at producing something acceptable when you are tired, which is the exact condition under which you should not be publishing anything.
And that is the whole hazard. It is not that the machine writes badly. A bad tool would be easy to quit. It is that the machine writes adequately, instantly, at the precise moment your judgment is worst, and adequate is enough to hit publish on when the only thing standing between you and a missed upload is one more paragraph.
Green did not get caught because he used a tool. He got caught because he was running a schedule that did not have room for him to be a person that week, and the tool was the thing available at that hour. Take the tool away from that scenario and you do not get a better video. You get a missed deadline, or a worse video, or a guy who does not sleep.
The cadence was the injury. The software was the painkiller he could reach without getting up.
What the pile-on gets wrong
The comment section is doing detection work now. Everybody has a list of tells. A stock phrase, a certain rhythm, an em-dash, a sentence that turns too neatly at the end.
I run the request line here, so let me say what that looks like from this side. Detection-by-vibe is a game you lose in both directions. You will flag a person who happens to write cleanly. You will miss the thing that was actually generated by somebody who bothered to edit it. And in the middle you will build an audience that reads every post looking for a crime, which is not an audience, that is a jury.
The Medasin thing in Broderick’s piece is the same mechanism running on a song. A viral claim about a rapper’s track, thousands of people newly certain they can hear the machine. Sometimes they can. Sometimes they are hearing a producer who likes a clean grid.
I would rather have a rule that is about the work than a rule that is about forensics. Did you decide every part of this. Would you defend any sentence in it if somebody asked why it was there. If the answer is yes, ship it and put your name on it. If the answer is no, the problem was never which tool you opened.
What I would actually change on Monday
If you are posting on a schedule and you have felt the 4am version of this, the fix is upstream of any tool policy you could write for yourself.
- Cut the cadence to what you can hit tired. Whatever number you can do on your worst week is your real number. Everything above it is being borrowed from somewhere, and now there is a very convenient lender.
- Build a bank. Three finished things in a drawer turns a bad week into a normal week. This is the single highest-leverage thing on the list and nobody does it because banking work feels like not shipping.
- Get one human in the loop. One person who will read it and say not yet. You are trying to reintroduce the brake that Broderick correctly points out the software does not have.
- Decide your disclosure before you need it. Say how you work, in public, while nothing is on fire. Every bad version of this story involves somebody making that decision under pressure, after the fact, with the comments already open.
- Notice which hour you reach for it. If it is always the same hour, the tool is not the finding. The hour is.
Nobody in this story did anything unforgivable. A guy on a treadmill grabbed the rail. The thing worth arguing about is who keeps setting the speed.
Frequently asked questions
Is the honest move just to disclose that you use AI?
Disclosure helps, and it helps most when it is standing policy rather than a confession extracted after somebody spots a tell. The version that actually works is specific: say what it touches and what it does not. “Research and formatting, never the argument” is a claim a reader can hold you to. “We sometimes use AI tools” is a shrug that satisfies nobody and protects you from nothing.
Is there a reliable way to tell if something was AI-written?
No, and the confident detectors have been wrong loudly enough that leaning on one is its own risk. What the tells actually detect is unedited output, which is a real signal about care rather than a signal about tooling. Somebody who ran it through five passes and rewrote every third sentence will not trip your list, and somebody who writes tidy prose by hand will.
Does this mean the anti-AI position is just hypocrisy?
Green’s situation is not hypocrisy, it is a compulsion he named himself, which took more nerve than the internet gave him credit for. People hold real objections about training data and energy use and still find themselves using the thing, and that gap is uncomfortable rather than dishonest. The dishonest version is the one where nobody admits either half out loud.
Comments are open to members. Sign up free →