Add Chain of Thought to Podcasts

[conorbronsdon]

Summary

Add Chain of Thought to the existing Podcasts section. I host and publish the show, which features practitioner interviews about building and operating AI systems.

Two examples of its comprehensive agent-engineering coverage:

• Vercel's Playbook for AI Agents, with CTO Malte Ubl: moving from an agent prototype to production, with concrete examples from developer tools and security workflows.
• Practical Lessons for GenAI Evals, with Chip Huyen and Vivienne Zhang: evaluating task completion, tool selection, parameters, and failure points in agent workflows.

Both have public transcripts and show notes. The Chip Huyen/Vivienne Zhang panel was recorded at Galileo's Productionize event; Galileo sponsored that episode, and I worked there at the time. The proposed entry links to the show rather than adding individual episodes across multiple topic cells - we have a ton of episodes covering agent memory, context + harnesses, architecting AI agents and much more.

Resource metadata (for additions)

• Title: Chain of Thought
• URL: https://chainofthought.show/
• Author / org: Conor Bronsdon
• Resource-type row: Podcasts
• Topic cell (T1–T21): Not applicable; the existing Podcasts section is not divided into topic cells.
• Provenance (who cites it?): Chain of Thought is already listed in these independently maintained GitHub resource collections, verified on September 9, 2026:
  • awesome-datascience: Podcasts
  • awesome-mlops: Podcasts
  • awesome-data-engineering: Podcasts
  • awesome-generative-ai: Discoveries / Podcasts

The show also appears in HushflowAI's AI podcast directory.

Checklist

• I read CONTRIBUTING.md.
• This is a resource (article/book/course/paper/talk/cookbook/benchmark/etc.), not a pure tool.
• I placed the entry in the strongest-fit matrix cell (no cross-posting except Trending/Milestones/Core).
• The link resolves and uses the canonical URL (no tracking params, no shorteners).
• The one-line description explains what you'll learn / why it matters, not marketing copy.
• The entry isn't already listed elsewhere in the README.
• Formatting matches neighbouring entries (order, icons, shields).
• awesome-lint and markdownlint pass locally (or CI will verify).

Validation

Verified commit 44b14f3 in Linux with Node 20:

• markdownlint-cli2 0.18.1: all five Markdown files checked, zero errors.
• awesome-lint 2.3.0: the repository's exact workflow wrapper passed (exit 0). The raw command reported only the two GitHub topic metadata diagnostics that the existing workflow explicitly excludes; no content diagnostics remained.
• git diff --check passed.