Shipping a daily tech podcast solo for ten years: lessons from Tom Merritt

Executive overview

Most content creators burn out or quit. Tom Merritt has shipped Daily Tech News Show five days a week since 2013 — without missing a planned episode.

The key isn't superhuman discipline. It's building systems, accountability structures, and a balanced editorial mindset that makes showing up the default.

Consistency compounds: the streak itself becomes the motivation, and the audience becomes the accountability partner.

Going independent: the decision and the runway

• Left TWiT in 2013 after being let go for working remotely; used severance as runway
• Had a friend (Brian Brushwood) already going independent who provided advice and encouragement
• Patreon launched ~6 months before DTNS — timing was critical; an earlier launch would have forced an ad-only model
• Initial plan was ads only; switched to Patreon after Cord Killers succeeded with it
• Early Patreon goals were public and milestone-based: hit X patrons, unlock a weekly co-host
• Within a year, had brought on one co-host per day of the week

Living with the fear of failure

• Fear that the whole thing could "fall apart at any moment" persisted for the first five years
• Difficult days came from content pressure, audience criticism, and at least one threatening audience member
• Negative criticism lingers far longer than praise — the asymmetry is real and never fully goes away
• The audience's positive reinforcement was the thing that "always turned him around" on hard days
• It took until year 8–9 before DTNS felt like a genuine going concern rather than something that might fizzle

How the daily show actually gets produced

• Morning: scan RSS/Feedly, mark stories; shared Feedly account so the whole team can flag items
• 9–10am: fill in the rundown (discussion stories vs. quick hits)
• 10–11am: write intros and notes, distributed across the team
• 11am–12pm: clean up, check for typos, monitor for late-breaking news
• 12pm: Discord voice call to review the rundown and set timing
• 12:45pm: StreamYard tech check
• 1–2pm: live show
• 2–2:30pm: post-production notes and wrap

Building accountability into the system

• A live audience streams on Twitch and Discord — they notice and ask if you don't show
• Has done shows from airports, from a car during a move, from anywhere rather than miss
• The streak itself is a forcing function: "the only reason I don't miss a week is because I haven't missed a week"
• Don't rely on personal willpower alone; build in external accountability (co-hosts, live audience, public schedule)
• Taking all federal holidays off eliminates the cognitive load of deciding what days are off

Handling criticism without becoming defensive or numb

• Can't simply "don't read the comments" — the show is built on reading emails and comments
• Default response: wait, write the angry reply to vent, delete it, then respond assuming the most charitable interpretation
• ~75% of the time the critic replies with: "I came off too harsh — what I meant was..."
• If someone is still hostile after a good-faith response, it becomes easier to discount them
• Look for the real complaint behind the surface complaint — "you called Apple great" usually means "you don't cover Android enough"
• Run proactive surveys: ask people what they hate about the show before they have to tell you
• Address public criticism publicly on the show — it closes the loop for the person and the wider audience

Staying balanced and avoiding pundit spin

• Natural tendency toward empathy: can see another person's point of view before reacting
• Also naturally contrarian — if everyone's thinking X, the instinct is to look for the counterargument
• Fear of corrections motivates thorough preparation: "What is the pilot going to say about this? Can I find that before I need them?"
• Time inside organisations (CNET, TWiT) taught him that internal motivations are always more complex than outside observers assume
• Avoids extreme takes because they stop being informative — the goal is to change the listener's understanding, not generate reaction

Using AI in a content workflow

• ChatGPT is weak for nuanced multi-sided coverage — it's trained on sources that aren't doing that work
• Useful for shortening and tightening a paragraph or two, though output still needs editing
• Midjourney (via co-host Veronica Belmont) used for Sword and Laser thumbnail art — works well
• Best use found: feeding ChatGPT context about a topic and asking it to write the next paragraph — it knows itself
• Eleven Labs voice cloning: useful for short clips (lost-voice situations, intros); quality degrades at longer lengths