Mostly Technical 124: Old Man Yells At Cloud
Mar 24, 2026
They debate building Solo versus using Faster.dev and which path is likelier to pay off. They weigh pros and cons of AI for bespoke internal tools and managing technical debt. They explore agentic dev environments, agents spawning agents, and Solo’s MCP architecture. They touch on fundraising timing, early revenue milestones, and a spoiler-filled chat about Project Hail Mary.
AI Snips
Chapters
Books
Transcript
Episode notes
Auto ScreenFlow Replaces Manual Exports
- Ian built Auto ScreenFlow to automate ScreenFlow exports by running a host/client app pair between his MacBook Pro and Mac Studio.
- The MacBook client rsyncs files to the Mac Studio, AppleScript launches ScreenFlow to export, then the host uploads the MP4 to Cloudflare R2 for Faster.dev processing.
Automate Processes Into Reproducible Code
- Building many small internal tools increases maintenance burden and creates technical debt that will break with OS upgrades or machine changes.
- Ian's solution: encode every operational step into deployable code and scripts so processes are reproducible and not reliant on memory.
Centralized Guarded Orchestration Beats File System Claws
- A centralized dashboard with guarded AI tools (a 'spiritual claw') can orchestrate many small scripts while providing safe, project-scoped actions.
- Use Laravel AI SDK to expose constrained tools/agents that call guarded endpoints like 'redeploy' instead of letting agents act directly on systems.
