The Exit Interview: JP Phillips

Source: fly.io Date: 2025-02-12 URL: https://fly.io/blog/the-exit-interview-jp/

Summary

Exit interview essay with JP Phillips, a senior engineering leader departing Fly.io after four years. Phillips reflects on Fly Machines and the flaps gateway as his primary accomplishment, highlights the finite state machine design in flyd (no central coordination required), and credits corrosion2 (gossip-based SQLite state distribution) as the most impressive colleague work. He’s candid about organizational challenges: lost strategic focus, inconsistent communication, frequent direction changes.

Implications

Edge deployment economics / infrastructure substrate. The interview is a useful internal map of Fly’s architecture priorities and where the bodies are buried. Phillips’ praise for corrosion2 — a CRDT-based gossip system exposing real-time global machine state via SQLite — confirms it’s load-bearing infrastructure, not a prototype. His critique of organizational direction is worth noting: it signals that Fly’s rapid product expansion (Sprites, MCP, Kubernetes, GPUs) may be creating coherence debt internally even as the external narrative stays sharp.