The Feedback Loop Is the Teacher: Why Students Should Publish Daily

I have written two essays on this site about screens, and both of them are warnings. One is about how feeds are engineered to hold attention. The other is about how recommendation systems shape what you think without your noticing. I stand by both. So it may seem strange that this essay argues a teenager should be on a screen, in public, every single day.

The resolution is that the problem was never the screen. It was the direction. A feed runs one way, at you. A practice loop runs the other way, from you, into the world, and back. Same glass. Opposite machine.

The loop

Here is the loop in its simplest form. A student makes something small and puts it where someone else can see it. Someone responds. The student adjusts and does it again tomorrow. That is all.

It sounds too simple to be a theory of learning, but it is the theory of learning that every craft has always used. Musicians play for rooms. Writers get edited. Cooks watch the plate come back. The reason school produces so little durable skill is that almost nothing a student makes ever leaves the building or gets a response from anyone but the person paid to grade it. A fourteen-year-old can go a full year without a single piece of work being seen by a stranger. No craft has ever been learned that way.

Publishing daily fixes the loop by brute force. Not because any one post matters, but because the response arrives every day, and a person who gets a response every day improves at a rate that a person who gets one every semester cannot match.

Why daily, and why public

Frequency matters because the loop is the teacher, and a teacher who visits once a term is not a teacher. Daily is a forcing function. It removes the option of waiting until the thing is good, which is the option that kills most work before it exists. Austin Kleon’s Show Your Work! makes the case better than I can: share the process, not just the result, and share it before you feel ready, because you will never feel ready and the sharing is how you get there.

Public matters because a response from a stranger is worth ten from a friend. Friends are kind. Strangers are honest, or at least indifferent, and indifference is information. A post that gets no response has told you something. So has a post that gets the wrong response. Kevin Kelly’s old argument about a thousand true fans is usually read as a business model. For a teenager it is better read as a learning model: you do not need a crowd, you need a small number of real people who will keep telling you the truth.

The response can be a coach before it is an audience

The obvious objection is that a fifteen-year-old who starts publishing today will hear nothing back for months, because nobody is listening yet. That used to be the fatal flaw in this plan. It is no longer, and the reason is the thing I would build.

Before there is an audience, the response can come from a coach, and the coach can be software. Not software that writes the post. Software that reads it and says: your second paragraph makes the argument your first paragraph should have made; you used the word “just” four times; the person you are writing for would stop reading here; here is what a stranger would have to already believe for this to land. A daily post with a coach’s note is a complete loop even on a day when no human reads it. The audience, when it arrives, is a second loop layered on the first.

The design has to be careful about one thing. The coach must never become the writer. The moment a student can ask the tool to produce the post, the loop is dead, because the response is now about the tool’s work and the student has learned nothing. Paul Graham’s recent essay Writes and Write-Nots predicts a world split between people who can still write and people who have outsourced it, and he is right that writing is thinking and that outsourcing it is outsourcing the thinking. The coach reads. The student writes. That rule is the product.

What the mechanic looks like

If I were building this for a school, the daily unit would have three parts and only three.

The post itself, made by the student, in whatever medium they are practicing: a paragraph, a sketch, a thirty-second video, a landing page, a demo. Small enough to finish before school ends.

The coach’s note, generated on submission, short, specific, and about the work rather than the student. Two or three observations and one question. No grade.

One number, chosen by the student, that they are trying to move this month. Not followers. Replies from strangers, or minutes watched, or sign-ups, or the number of people who asked a follow-up question. The student picks it, the software tracks it, and the weekly review asks a single question: did the thing you changed move the thing you chose?

The most important thing about this screen is what is not on it. There is no feed. The student does not see a stream of other people’s work between them and their own. They see their post, their note, and their number, and then they leave.

The counterweight

Jonathan Haidt’s The Anxious Generation argues that the arrival of smartphones and social media in the early 2010s coincided with a sharp rise in adolescent anxiety, depression, and self-harm, especially among girls, and that the feed-based social platforms are a principal cause. Whether the causal case is as tight as Haidt says is contested among researchers. That the correlation is real, and that a lot of parents recognize it in their own house, is not.

I take that argument seriously, and I think it argues for this design rather than against it. Everything Haidt identifies as harmful is a property of feeds: infinite scroll, social comparison, engagement metrics, the performance of a self for an audience of peers. Nothing I have described has those properties. The student is not consuming. They are making, getting a response about the work, and leaving. The number they track is one they chose, about their craft, not about themselves. For a minor, the first audience should be small and real, a class, a mentor, a handful of customers, before it is the open internet. The loop works at any size. The feed only works at scale, which is the tell.

What this teaches that nothing else does

Publishing daily teaches the thing that school is structurally unable to teach: that your work exists outside your head, that other people will react to it in ways you did not intend, and that you can adjust and go again. A year of that produces a person who can take feedback without collapsing and give it without cruelty, who ships before they feel ready, and who has three hundred small pieces of evidence that they can make things. I described the ledger for that evidence in Prove It. The daily post is where the entries come from.

The screen is not going away. The only question is which direction it runs.