From the first time a 15‑year‑old coder heard a Phish set, the band became the soundtrack to a career. By 1998 he landed a tech job and began building distributed systems while listening to long, evolving jams. The music fed a rhythm that matched the complexity of backend services, turning code sprints into a continuous flow state.

During graduate school, he wrote a 200‑page dissertation on distributed systems while streaming Phish shows from Hampton or Alpine Valley and studying at Berklee College of Music. The dual focus sharpened his understanding of long‑term system design and live performance. After returning to Pittsburgh in 2021, he completed the thesis and continued to produce production software, all while the band’s improvisations echoed in his mind during daily coding sessions and meeting deadlines.

Today his role shifted to managing autonomous agents and short, context‑switching tasks, a stark contrast to the deep, uninterrupted focus he once relied on. The music now feels out of phase with his work; he can no longer enter the flow state that powered his career. The loss of that creative rhythm underscores how changing engineering workflows can erode long‑term fulfillment for developers in today's profession.