Stop Listening to Dev (or Start Up) Podcasts. They're Making You Worse.

Most commentators are either a has-been or someone who never made the team. There is great content, thats not the argument here.

It's not hate. That's just true. Sports. Music. Business. Tech. The people in the booth talking about the game are not the ones playing it.

If you're a developer right now spending more time consuming content about building than actually building, you might be sitting in the booth and not realizing it.

This is the tap on the shoulder.

The content trap looks exactly like productivity.

You know the loop.

Open the laptop. Today's the day. But first, check that Reddit thread about the new framework. Then 20 minutes of a podcast where two guys debate which LLM is better. Then a tutorial you skim, bookmark, and never come back to.

Two hours later your editor is still empty.

But you feel like you did something.

That's the trap. Your brain got fed technical language and new ideas so it gave you the same reward it would've if you actually built something.

You didn't.

And that gap compounds. Quietly. Over weeks. Over months.

I'm not calling you out. I've been in that loop. I'm just telling you what it looks like from the outside.

Nobody buys a ticket to hear the commentators.

I'm from Ottawa, Ontario, Canada. Grew up on hockey.

And every fan knows this instinctively. You don't go to the game for the broadcast. You go to watch who's on the ice.

Most dev podcasts. Most AI Twitter threads. Most "10 tools you need" posts. That's commentary. And commentary has value. But it's not the game.

If your goal is to build, to ship, to actually play, you need to get on the ice.

Touch the puck. Put your name on a repo. Push something live that could break.

I'm on the ice right now. Player-coach. Still getting hit. Still learning every shift. But the view from inside the game is nothing like the view from the booth.

Talk to devs who are building. That’s happening here on Dev. Get in their comments, ask questions, go to Hackathons, make friends. Watch what they ship. Not what they say.

That's your peer group. Not the podcasters.

The devs pulling ahead aren't smarter. They just closed the tab sooner.

Go look at their GitHub profiles. The ones getting hired. Getting funded. Getting noticed.

Their repos aren't clean. Their READMEs are half done. Their commit messages are gibberish.

That's what building actually looks like.

They didn't wait until they felt ready. They started before the tutorial was finished. They asked Grok stuff mid-build. They shipped ugly and fixed it in public.

The gap between them and the dev who "almost started that project" isn't talent.

It's the moment they closed the browser and opened the editor.

Backboard shipped major updates last week, looking back at the original, I can’t believe we’re the same company. 🤯

You're closer to the bleeding edge than you think.

If you're reading this, you are closer to the frontier of technology than almost everyone on the planet.

The non-technical world is watching AI happen to them. They don't know what an API is. They don't know what a context window does. They're not dumb. They're just not in this world.

They need people who can build things that work and explain why they matter.

That's you.

But only if you build.

The risk right now is you stay in the consumption loop long enough that someone who knows less than you but ships faster ends up defining what gets built.

Not because they're better. Because they started.

The fastest way to learn is to build something that breaks.

Not a course. Not a cert. A project that breaks in public and forces you to fix it.

When you ship something you hit real problems. Not textbook problems. Real dependency conflicts. Real "why is my state disappearing between sessions" moments. Real user feedback that makes you rethink everything.

That's where learning actually lives.

Every senior dev you look up to got there the same way. Building. Breaking. Fixing. Doing it again while people watched.

If you want to skip the part where you spend two weeks wiring up memory and state before you even touch the thing you want to build, Backboard handles that. Free state for life on signup. Not the point of this article. But it kills one of the quietest excuses I hear from devs who don't ship: "I'm still setting up infrastructure."

You don't need permission. You need a deadline and a publish button.

Pick one thing. One idea you've been sitting on.

Give yourself 48 hours. Ship it.

Ugly is fine. Three views is fine. What matters is you broke the loop.

After my last article went viral on here, the DMs I got weren't asking for resources or reading lists. They were all some version of the same thing:

"I needed someone to tell me to stop overthinking it."

So here it is again.

Stop overthinking it. Close the tabs. Open your editor. Build the thing.

I'll see you on the ice.

PS: My one book to recommend that aligns with this post would be Extreme Ownership.