- Simplify flatten_vault API to return usize instead of MigrationResult struct
- Add KEEP_FOLDERS: attachments/ and _themes/ alongside type/, config/, theme/
- Use HashSet for collision tracking in unique_filename
- Update wikilinks from path-based [[folder/slug]] to title-based [[slug]]
- Clean up empty directories after flattening
- Flatten demo-vault-v2: move all notes from type-based subfolders to root
- Update smoke tests for flat vault structure
- Remove migrate_to_flat_vault from repair_vault (one-time migration only)
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The Refactoring podcast is the second major content channel alongside the newsletter. Bi-weekly episodes featuring conversations with tech leaders, engineering managers, and founders create a different kind of depth and relationship than written content alone. This responsibility covers the full production pipeline — guest sourcing, recording, editing, publishing, and performance analysis — and plays a critical role in audience growth and brand positioning.
Scope
Sourcing and scheduling guests who bring genuine insight on engineering culture, leadership, and building
Preparing for and conducting interviews that are conversational, substantive, and worth re-listening to
Managing the post-production pipeline: editing, show notes, and publishing on schedule
Tracking downloads and engagement metrics to understand what resonates with the audience
Maintaining a guest pipeline that is at least 4-6 weeks ahead of the publishing calendar
Cross-promoting episodes through the newsletter and social channels to maximize reach
Current state
The podcast is shipping consistently at two episodes per month, and download numbers are trending upward. Guest quality has been strong, with several recent episodes generating above-average engagement and social sharing. The production pipeline with person-paco-furiani handling operations has reduced the turnaround time from recording to publication significantly.
The main challenge is guest pipeline management. Outreach tends to happen in bursts rather than steadily, which occasionally creates scheduling pressure. There is also an opportunity to be more strategic about guest selection — aligning episode topics with upcoming newsletter themes to create a more cohesive content ecosystem. Analytics review happens but is not yet systematic enough to drive data-informed decisions about format and topic selection.
b3126044e8