Quality Inputs Shape Quality Outputs
contents
Your inputs aren’t neutral
Pay attention to your own head for a day and you’ll notice something uncomfortable. The phrases you reach for, the things that irritate you, the comparisons that pop up unprompted, a lot of it is just an echo of whatever you’ve been consuming. What goes in becomes the raw material for what comes out: your thoughts, your mood, your taste, your sense of what’s normal and what’s worth wanting. Inputs aren’t neutral. They’re training data, and your attention is the model being quietly fine-tuned on whatever you feed it most.
What this solves
- Treats media as inputs that train you, not entertainment that passes through.
- Gives a four-bucket test for sorting what’s worth consuming.
- Picks format by function, so you stop confusing “productive-looking” with “useful.”
Useful and productive aren’t the same thing
Here’s the distinction most media advice misses. Not all useful media looks productive, and a lot of productive-looking media isn’t useful at all. The two get conflated constantly, and the conflation is what keeps smart people stuck consuming the wrong things while feeling virtuous about it.
A technical walkthrough is the cleanest example. Watched while you’re actually building the thing, it’s genuinely useful: you hit a wall, you find the answer, you keep moving. Watched instead of building anything, the exact same video is procrastination wearing a tutorial’s clothes. It feels productive because it’s “learning,” but nothing left your head and entered the world. Meanwhile a novel, which looks like pure leisure, can be doing real work, resting your attention, stretching your sense of other people, refilling the well you draw from. Prestige is a terrible guide here. The question is never how respectable the input looks. It’s what the input is actually doing to you.
Sort everything into build, support, recover, or waste
I stopped asking whether media was “good” and started asking what function it served. Four buckets, and almost everything I consume drops into one of them.
| Bucket | What it does | Example | The tell |
|---|---|---|---|
| Build | Feeds something you’re making | Docs for the bug you’re fixing | Points at output |
| Support | Maintains you, builds nothing directly | A podcast on a walk | Good in moderation, noise in excess |
| Recover | Rests you | Fiction, a film you chose | You come back more capable |
| Waste | Stimulates without building or resting | Algorithmic short-form | You feel more depleted after |
Build is input that feeds something you’re actively making or becoming. The documentation for the bug you’re fixing. The book on the skill you’re building. It earns its place by pointing at output.
Support is input that maintains you without directly building anything. A podcast on a walk, a conversation, the article that keeps you oriented in your field. It’s the connective tissue around the work, valuable in moderation and noise in excess.
Recover is input whose whole job is to rest you. Fiction, a film you chose on purpose, music, genuine downtime. This bucket is not a lesser one. Recovery is a real function, and pretending you don’t need it is how people burn out while consuming nothing but “productive” content. Sleep is the deepest form of this bucket, and the one most worth protecting.
Waste is input that does none of the above. It stimulates without building, supporting, or actually resting you, and leaves you a little more depleted than it found you. Most algorithmic short-form lives here. The tell is how you feel after: not built, not maintained, not rested, just used.
Choose the format by what you need from it
Once you’re sorting by function, the format almost picks itself. The mistake is reaching for a format by habit, the feed because it’s there, the podcast because the silence felt weird, when a different one would serve the actual need far better.
If you’re building, a book or the real documentation usually beats a video, because text lets you move at your own pace and a repo lets you do the thing instead of watch it. If you need support, a podcast or an article fits the gaps in a day. If you need to recover, this is the one most people get wrong. They reach for short-form video to unwind and end up more wired than when they started. Fiction, in my experience, is genuinely better recovery than a feed: it rests attention instead of fragmenting it, and you come back from a chapter calmer rather than twitchier. And sometimes the right format is no input at all. Silence is a legitimate choice, and a podcast that fills every quiet moment stops being support and becomes noise that crowds out your own thoughts.
A five-minute audit of what’s training you
Sorting in the moment handles the day-to-day, but the inputs that quietly shape you most are the recurring ones, the subscriptions, feeds, and follows you set up once and never reconsider. So every so often I run a fast pass over them with the same four buckets. What is this channel, this newsletter, this app actually doing for me right now? Build, support, recover, or waste?
The answers drift over time, which is the point of checking. The feed that was genuinely useful when I was learning a thing becomes waste once I’ve moved on, but it stays subscribed out of pure inertia. The audit catches that lag. It takes five minutes, and it usually ends with me unfollowing or muting a couple of things that had quietly slid into the waste bucket while I wasn’t paying attention. Inputs you chose on purpose age better than inputs you simply never removed.
A media diet that supports action, recovery, and judgment
So the goal here isn’t a stricter, more joyless intake. It’s a media diet built around function, one that supports the three things that actually matter: action, recovery, and judgment. Inputs that help you make things, inputs that genuinely rest you, and inputs that sharpen how you see rather than just filling time.
In practice the audit is fast. When I catch myself consuming something, I ask which bucket it’s in right now, because the same input changes buckets depending on what I’m doing. The walkthrough is build when I’m coding and waste when I’m avoiding it. The podcast is support on a walk and noise when it’s papering over silence I should sit with. This is the same instinct behind treating unmaintained accounts and subscriptions as inventory: most of the cost is invisible, and the fix is asking what something is actually doing for you, not what it claims to be. Cut the waste, protect the recovery, and aim the rest at something you’d endorse later. Your outputs are downstream of your inputs whether you manage them or not. You may as well choose what trains you.