Staying current with AI without getting overwhelmed.
How you can go from "interesting long podcast episodes" into a usable intelligence layer — and the curated sources that survive the trust-and-test filter.
Use one or two curated, high-signal sources. Schedule the time — don't doomscroll. Test claims yourself before forwarding them. Find one podcast where you're not the smartest person in the room, and listen with your AI open.
The podcast I keep coming back to is Moonshots with Peter Diamandis. To make it actually usable across episodes, I built a distillation layer — briefs, tools & tech, people & companies, claims to verify, and concrete next moves.
moonshots.botgui.de
Each Moonshots episode distilled into five layers: briefs, tools & tech mentioned, people & companies to watch, claims to verify, and actionable signals. Free to browse.
Open moonshots.botgui.de →The overload problem
The AI commentary landscape is mostly noise. Two new models every week. A "breakthrough" every Tuesday. Every influencer with a ring light has hot takes on something they couldn't have explained six months ago. The signal-to-noise ratio is bad and getting worse, and the rational response is not consume more — it's the opposite.
But "ignore it" doesn't work either. The applicable slice of AI development — the part that actually changes how a small firm operates — is moving fast enough that being three months behind costs you real things. The question isn't whether to pay attention. It's how to pay attention without burning your week on it.
Here's the workflow I've landed on.
The four-line filter
Four rules, in the order I actually use them:
1. Limit inputs.
One or two curated sources per format. One daily newsletter for breaking news. One YouTube channel for weekly recaps. One community subreddit if you want depth. Not twelve. Not "I'll subscribe and unsubscribe later." Two.
2. Schedule it.
Fifteen to thirty minutes in the morning, or a single weekly recap on the weekend. Not a feed you check twelve times a day. The feed-checking habit is the problem; the content is just the excuse.
3. Build, don't just read.
The fastest way to know whether a tool matters is to try it on something real. ChatGPT, Claude, Copilot — pick a piece of your actual workflow and run it through. Having read about a tool and having used a tool are different categories of knowledge.
4. Filter for relevance.
Ask: will this matter to me in three to six months? If no, skip. The world's most impressive demo of a thing you will never use is still a thing you will never use.
Follow builders, not hype
The voices worth listening to are people building, not people commentating. Researchers publishing papers. Engineers shipping tools. Founders running companies. The signal density on those sources is dramatically higher than on the influencer tier, because they have skin in the game — they have to actually make something work.
A rough source landscape, not an endorsement of any one in particular:
- Newsletters: The Rundown AI, TLDR AI, The Batch (Andrew Ng's team).
- YouTube: AI Explained, Matt Wolfe.
- Communities: r/LocalLLaMA, r/MachineLearning.
Pick one from each row. The point isn't that these are the right answers — it's that you should have an answer, and "all of them" is not it.
Trust, but test
There are a lot of voices in this space, and most of them are confident about things they don't fully understand. Including, occasionally, me. The defensive move is not "find the one source you trust completely" — that source doesn't exist. The defensive move is to test claims yourself before forwarding them.
This applies to AI outputs too. When the model tells you something authoritatively, the question to ask isn't is this right? — it's what would have to be true for this to be wrong? Then go check the thing that would have to be true.
The second-best move I've found is to find one podcast where you are not the smartest person in the room, and listen to it consistently. Then listen with your notebook out and your AI open. When you hear something you don't know, ask the AI. When you hear something that could matter, ask the AI: how does this apply to me? A podcast that stretches you, plus an AI that contextualizes — that's the highest-leverage AI-learning loop I've found.
The podcast — Moonshots
For me, that podcast is Moonshots with Peter Diamandis. Four core hosts, each from a different angle:
- Dr. Peter Diamandis — founder of XPRIZE and Singularity University.
- Dave Blundin — founder and general partner of Link Ventures.
- Salim Ismail — founder of OpenExO.
- Dr. Alexander Wissner-Gross — computer scientist and founder of Reified.
They're diverse, interesting, and actionable. Different beats, different incentive structures, decent disclosure when they're talking about something they have a position in. They will say things that are wrong. They will say things that are very right. The job isn't to absorb everything — it's to recognize which is which.
There's even some "not investment advice" (wink) buried in there, if you listen for it.
The distillation layer
The problem with a 90-minute podcast is that 90 minutes is a lot of time and your memory is bad. After three or four episodes, the threads start to blur — who said what, which company keeps coming up, which prediction was Peter's and which was Salim's.
The site turns each episode into five layers:
- Briefs. What changed, what matters, why it's worth paying attention to. The core signal extracted from the episode.
- Tools & tech mentioned. Every model, platform, workflow, robot, lab, protocol, or piece of software that came up. The kind of inventory you can actually go investigate.
- People & companies. A map of who keeps showing up — OpenAI, Google, Anthropic, NVIDIA, Tesla, Demis Hassabis, the White House. Over time this becomes a pattern database.
- Claims to verify. Strong claims pulled out with source status, so you can separate interesting podcast statement from decision-grade fact.
- Actionable signals. Concrete next moves — try a tool, add a company to watch, compare two models, verify a market claim, run a small experiment, track a policy or regulation shift.
Pattern recognition across episodes
The real value isn't one episode. It's recurrence.
Are AI agents replacing SaaS? Is compute and power becoming the bottleneck? Are humanoid robots moving from demos to production? Which companies keep being central? Which predictions are getting stronger and which are getting weaker? You can't see those patterns inside one episode. You can see them across twenty.
That's the long-arc payoff of the distillation layer — and frankly the part of the project I find most useful for my own thinking.
The north star
The whole point of all of this is to go from this:
"I listened to a podcast."
to this:
"Here are the 3 things I should investigate, the 2 companies to watch, the 1 claim to verify, and the experiment or workflow I should try this week."
Every episode should produce that output. If it doesn't, the listening was entertainment, not intelligence. That's fine — sometimes entertainment is what you want. Just don't confuse the two.
Why this matters for an engineering firm
Bailey is a civil engineering firm. The reason I invest time in this workflow isn't AI-for-AI's-sake. It's that the applicable slice — the tools that change how a small firm operates, the signals about regulatory and infrastructure trends — those compound into real wins for our clients and for us.
It's the same discipline we apply to land-use intelligence: filter for signal, document the method, ship the result. AI is method, not magic.