If You Applauded, I Failed
Musonius Rufus said applause means the lesson didn’t land. My dashboard only counts applause.
I’ve published nearly two hundred articles in a little over two years. I can tell you how many people liked each one. I can tell you which ones got restacked, which ones pulled in new subscribers, and which ones got a comment that said “great piece.”
I can’t tell you what a single one of them changed.
The Flute Player
Musonius Rufus taught philosophy in Rome in the first century. Much of what we know about him comes from others. Aulus Gellius recorded a curious story about how Musonius interacted with an audience.
Musonius didn’t like applause. When listeners shouted praise, gestured, and got swept up in the rhythm of a speaker’s words, he said speaker and audience were both wasting their time. They weren’t at a philosophy lecture. They were at “a flute-player’s recital.”
His reasoning was simple. If what the philosopher says is actually working, if it’s pointing at a fault the listener has and offering a cure, that listener “has no time or leisure for continued and extravagant applause.” He’s busy. He’s uncomfortable. He should “show changes of countenance,” Musonius said, because he’s recognizing himself in what he’s hearing, and it isn’t flattering.
Then Musonius reached for Homer. When Odysseus finished telling the Phaeacians about his years of hardship, they didn’t jump up cheering. They were “one and all silent, as if amazed and confounded.”
That’s the response Musonius wanted. Silence. The kind you get when someone stops performing a reaction because they’re too busy having one.
I Already Fixed This Once
I thought I’d dealt with this.
My first run at writing on Medium had gone sideways because I was chasing numbers, building a following that wasn’t actually reading. When I came back, the rule was connection over metrics. Write for the people who read, not for the count.
I meant it. I still mean it. But read Musonius and look at what “connection” turned into.
A heart is applause. A restack is applause with a share button. “Great piece” is applause in a sentence. Even a long comment can be applause if what it says is “I agree.” I didn’t stop measuring approval. I swapped a loud kind for a polite kind and called it connection.
Every number the platform gives me is the same shape. Opens, likes, shares, new subscribers. There is no dashboard for “someone handled a code review differently on Tuesday.” There’s no metric for “someone didn’t send the email.” The only things I can count are the things Musonius said don’t count.
Code Tells You
I’ve spent twenty-five years in a craft that tells you, quickly and without caring about your feelings, whether you were right. The build passes or it doesn’t. The test goes green or red. Production either holds or pages you at 2 a.m. You can be wrong for a long time in software, but you rarely get to be wrong without finding out.
Writing has none of that. If a piece works, it works somewhere I’ll never see: in a reader’s head three weeks later, in a meeting I’m not in, in a decision nobody connects back to an article.
The feedback loop isn’t slow. It isn’t there.
So I have a craft with a brutally honest feedback loop and a practice with no feedback loop at all, and I’ve been treating the applause like a test suite.
What You Measure, You Write Toward
If I can’t measure what I want, I’ll end up chasing what I can measure. Every developer has watched this happen to a team. Put a metric on a dashboard and the work bends toward the number. Story points inflate. Coverage climbs while the tests stop testing anything.
There’s no reason I’d be immune to that just because the dashboard is about my writing.
I write titles like “Hope Is for Losers.” I’ve always said the provocation has to be paid off, that a sharp title has to earn a real argument in the body. I believe that. But I also know which titles get clicked, and I know which ones get hearts. When I reach for the sharp version, am I reaching for the reader who needs to be stopped, or for the applause?
I don’t know. I genuinely can’t tell, and nothing I have can tell me.
The Exit I’m Not Taking
There’s an easy way out of this, and it sounds very Stoic. The effect on readers isn’t up to me. Only the work is. Write well, let go of the outcome, move on.
Some of that is true. I don’t control what happens in someone else’s head.
But it’s also exactly what you’d say if you wanted permission to never check. It turns “I can’t measure this” into “I don’t need to,” and those aren’t the same thing. Musonius didn’t say ignore the audience. He said watch them more carefully, and stop mistaking noise for evidence. He was paying attention to faces.
I don’t have faces. I have a dashboard.
Where That Leaves Me
I don’t have a fix. Turning off like counts wouldn’t make the effect visible. Asking readers to tell me what changed would just invite a more sophisticated kind of applause. Even this piece is a little suspect. It’s built to make a reader nod, and nodding is the quietest applause there is.
What I have is the question, and I’d rather carry it honestly than pretend the numbers answer it. Nearly two hundred articles, and the best outcome I can hope for is one I’ll never get to see.
If this one works, I probably won’t hear about it.
👉 If you enjoy reading this post, feel free to share it with friends!
Or feel free to click the ❤️ button on this post so more people can discover it on Substack 🙏
You can find me on X and Instagram.


Discussion about this post