Hey, I had such a blast in our chats and got totally nerd-sniped by the thing you’re creating.

I made this doc, mostly while walking to and from the (so please excuse its crudeness). But it’s my pitch for the first quarter of working with a video creator.


Reinforce. Connect. Create.


Reinforce the addition of the podcasts with platform-specific capabilities: YouTube cards (dynamic but disruptive).

This helps distinguish video as a unique (higher fidelity) Syntax. experience.

We add short-form, vertical videos for max re-distrubution. And include a callout to the related episode: β€œLearn more about {X} at syntax.fm/{#}

These are a few candidates I pulled from the latest episode, that could use visual/educational reinforcement.

01:04Drizzle is a modern ORM in TypeScript.
02:57Why do I need Drizzle-Kit?πŸ’–
04:30How does Drizzle-Studio compare to other MyQSL web admins?πŸ’–
05:30Database viewer showdown: SQL Pro, TablePlus, PHPMyAdmin, mongodb compass, etc.πŸ’–
06:11What is MD5 hashing?
06:50Eradicate slow queries with Drizzle Studio Benchmarks
09:22Relationshal Databases compared: which is best for your project?πŸ’–πŸ’–
09:49Create an [@rds] on [@service_provider] for free!(Neon, Supabase, Vercel, Cloudflare, Upstash, Xata, Railway, Payload, PlanetScale)πŸ’–πŸ’–
13:445 differences between MySQL and PostegresπŸ’–πŸ’–πŸ’–
14:42Build a fullstack modern web app with these generous free teirs…
14:44Never create a new database β€” use Drizzle prefix instead!
14:53This whole database is a single file!
18:17Which relational Database is right for you?
14:53SQLite β€” a file on your computer β€œyou got yourself a database runningβ€πŸ’–πŸ’–πŸ’–
15:50- DBEngine (start and stop database servers)
17:20Apple Messages and photos database are just SQLiteπŸ’–πŸ’–πŸ’–
18:17Why pick SQLite, Cloudflare D1, fly.io LiteFS, bun
19:00bun SQLite API built right in. Import with import assertions!πŸ’–
19:51Get started with bun
20:00bun import assertionsπŸ’–
21:20Defining schemas with drizzleπŸ’–
22:00What is [a DSL](https://en.wikipedia.org/wiki/Domain-specific_language?
24:00”You only need to use drizzle kit if you’re using it to handle migrations and creations”
25:42Let’s open it up: spelunking open source: habitpath.io
27:20SQL quickstartπŸ’–
28:30What is a relational database
30:00Drizzle ESLint plugin does wHAT??πŸ’–πŸ’–
31:00Include relations with with
32:00Find the internets secret solutinos with answer overflowπŸ’–πŸ’–πŸ’–
33:00ChatGPT shootout: drizzle vs PrismaπŸ’–πŸ’–πŸ’–
33:43The future of documentation: β€œAsk AIβ€πŸ’–πŸ’–
34:00Building AI-powered docs with inkeep. Could be a fun micro interview.
35:00Introspection schemas with Drizzle Pull
36:40Drizzle TypeScript completion magic in action πŸͺ„
38:00What drizzle-kit generate means for type-safety
41:00query vs select (orm vs β€˜raw’)πŸ’–πŸ’–
43:00Stop writing the same SQL query! Use views (aggregations) to codify common patternsπŸ’–
46:00Data getting out of sink? Use SQL transactions to ensure everything goes into the database at once.πŸ’–


Connect the dots between video, social, and website.

Explore a cooperative workflow, where high-priority videos are identified (before video podcast release).

See if we can record and insert video right into the video podcast, VH1 Pop-up video style. This is something that people loved in Storybook’s Storytime interview series.

Unlike the cards approach, above, this is completely non-disruptive to core content.

We could create some topical landing pages on the Syntax. website. /orm, /react, /node, etc. They could showcase all of the episodes with that as a topic. And eventually grow to include chnannel learning resources (See: Create).


Create new formats that establish the channel a broader education resource. Start with topics that were disproportionately popular on the podcast.

After my chat with Ben, I started thinking about higher effort, more exhaustive, more durable, non-podcast formats for channel uploads. I think this would provide a broader counter-point to news-driven formats.

There are two formats that might do well here. This is the shape they could take for the latest episode (if the response justified additional content):

  • The Syntax Guide to SQL: The 20 commands, operators, and features you HAVE to know.
    • Style: freecodecamp YouTube (guide)
    • Question: how?
  • A Brief History of ORMs: How they came to be and why they are still relevant.
    • Documentary style.
    • Question: why?

”What”, β€œwhen”, and β€œwhere” are well covered by the podcast.

This could tie in really well to the topic pages mentioned in the connect section.


Transcripting seems to prefer β€œCentury” not β€œSentry” πŸ˜…

Oops. "Century"