JP Phillips, the architect of Fly Machines, has left his position after 4 years to join another company. He cited a mismatch between his desired focus and the direction of Fly Machines as the reason for his departure. Despite this, he expressed pride in several key projects, including the development of deterministic and durable execution capabilities using Cadence technology. Phillips also highlighted the importance of platform components like corrosion2, which enables SQLite queries to access near-real-time information about any Fly Machine around the world. He praised the Fly Machines API, citing its ability to run workloads from an OCI image and API call across the globe, and noted that his most impressive achievement was building the Fly proxy team's codebase. In a lighthearted tone, Phillips expressed frustration with certain aspects of the platform, including GraphQL and Elixir, while also acknowledging the value of tools like OpenTelemetry for troubleshooting and debugging. He offered words of caution to future candidates regarding the company's management structure and communication style, but concluded by expressing gratitude for his time at Fly.io.