In a recent episode of the podcast, Quincy Larson sat down with Mike McQuaid, the lead maintainer of Homebrew and former GitHub principal engineer, to discuss the intricacies of open source work and the essential skills developers need as they move forward in their careers. With insights drawn from nearly two decades of experience in remote software engineering, McQuaid offers a detailed account of managing large-scale open source infrastructure projects, such as Homebrew—a Mac package manager utilized by millions of developers.
A key focus of their conversation was the challenge of balancing open source responsibilities with the demands of full-time employment. McQuaid, who also serves as CTO, emphasized the importance of sustainable project leadership and effective time management. He advocates for doing fewer things well and setting clear boundaries with users to foster a high-trust work culture.
Addressing the risk of burnout, McQuaid shared several strategies such as minimizing distractions, batching work, and recognizing the point of diminishing returns. He draws a pertinent contrast between the environments of well-funded tech companies and volunteer-driven open source projects, highlighting that maintainer sustainability should be prioritized over user feature requests, thus ensuring the project’s longevity.
The discussion also touched upon McQuaid’s philosophy on communication—advocating for directness and transparency rather than offering false hope. In handling criticism, he underscores the need to be receptive yet assertive in response. Overall, the conversation offers valuable insights into the dynamics of remote collaborative work and the future skills developers should cultivate.

Collections

Mike McQuaid, Homebrew's lead maintainer and former GitHub principal engineer, shares strategies for balancing open source maintenance with full-time work. He emphasizes sustainable project leadership through clear boundaries, effective time management, and prioritizing maintainer well-being over feature requests. Key practices include batching work, minimizing distractions, recognizing diminishing returns, and maintaining direct communication with users. The discussion covers burnout prevention, building high-trust remote work cultures, and essential skills for developers managing large-scale open source projects.

Balancing Open Source Work and Full-Time Employment with Mike McQuaid