Today I’m proud to announce the release of Homebrew 5.1.0. The most significant changes since 5.0.0 are expanded brew bundle support, brew version-install, new -full formula handling and installer updates.
https://brew.sh/2026/03/10/homebrew-5.1.0/
Great post here from Andrew, particularly on why Homebrew doesn’t need a NPM-style cooldown.
Should be obvious but seems it’s not: don’t spam OSS maintainers or coworkers with AI code you’ve not reviewed yourself.
For coworkers only, sometimes fine explaining your testing and why reviewed isn’t necessary e.g. a one-time script.
https://simonwillison.net/guides/agentic-engineering-patterns/anti-patterns/
It’s hard to understate just how much more productive coding agents are at some tasks in YOLO mode. Essential to have a good sandbox for this, though. My favourite so far is sandvault: no Docker nonsense needed.
https://github.com/webcoyote/sandvault
The year is 2068. All matter in the solar system has been consumed for energy. All energy is used for the system’s sole remaining purpose: AI generation of another new frontend for Homebrew.
The author and I are convinced AI is net positive in engineering today but worth engaging seriously with the downsides.
https://tomwojcik.com/posts/2026-02-15/finding-the-right-amount-of-ai/
Google continues to take money for malware pretending to be Homebrew installation.
There’s nothing Homebrew can do about this. Google needs to fix it.
Please put me in contact with someone at Google high enough level to actually fix it.
https://github.com/Homebrew/install/issues/1074
Andrew nails here many parts of what actually makes OSS maintaining hard work.
Empathy is needed more for OSS sustainability than money.
https://nesbitt.io/2026/02/13/respectful-open-source.html
“This new technology will replace developers!” is not a new thing.
Nice look at what some previous claims were (and how they resulted in more developers and more software).
https://www.caimito.net/en/blog/2025/12/07/the-recurring-dream-of-replacing-developers.html
Great take about the cultural requirements to create “10x engineers”
https://randsinrepose.com/archives/sometimes-your-job-is-to-stay-the-hell-out-of-the-way/
31 January 2026
Lessons for non-Ruby projects on non-profits, governance, money and access in open source, drawn from the RubyGems dispute.31 January 2026
Homebrew 5.0.0 released in 2025. Walk through the major changes in 5.0.0, improving expectations based on other package managers and what they can learn from Homebrew's approach.27 January 2026
Interviewed by Screaming in the CloudMike McQuaid explains how Homebrew grew from a side project into macOS’s de facto package manager and how the project is sustained today.
24 January 2026
Minimum Viable Management
David Yee, VP of Engineering at The New York Times and head of its new AI platforms and products mission, joins Mike McQuaid and Neha Batra for a candid, behind-the-scenes conversation about why institutions are built to resist change and what to do about it. They dig into hidden norms, choosing the right battles, translating “how things really work” and creating stability for teams while you deliberately destabilize the system just enough to move it forward.
16 January 2026
Interviewed by freeCodeCamp PodcastMike McQuaid joins Quincy Larson to discuss career lessons and the software engineering skills worth prioritizing next.
13 January 2026
Like many people who now work with computers, I was told as a child I spent “too much time on screens” and then built a career out of it.
09 January 2026
Minimum Viable Management
Performance reviews have a reputation for being stressful, confusing and often disconnected from reality. Too often they surface feedback that should have been shared months earlier or reduce a year of work into a single rating. In this episode, Mike and Neha unpack why reviews fail and how managers can turn them into a useful summary instead of a shock.
They explore what companies expect from performance reviews, what managers struggle with and what employees actually want to hear. The conversation covers documenting early signals, balancing positive and critical feedback, avoiding ruinous empathy and ensuring no one walks into a review surprised by the outcome. They also discuss practical ways to give feedback throughout the life of a project, align on growth goals and handle mismatches between perception and reality. A grounded, experience-based discussion for anyone responsible for giving or receiving feedback.
29 December 2025
Minimum Viable Management
In this episode, Mike and Neha are joined by Denise, an engineering leader and former colleague from GitHub and Pivotal, to unpack the reality of workplace politics and why ignoring them is not a neutral choice. Drawing on Denise’s LeadDev talk and hard-earned lessons from management and senior IC roles, the conversation explores political capital, information asymmetry, allyship and the idea of “table flips” as a finite currency.
Together they discuss when to spend influence, when to hold it back and how privilege shapes who gets heard. From advocating for promotions to using power responsibly on the way out of an organisation, this is a practical and candid look at how to navigate work under capitalism without burning out or selling yourself short.
19 December 2025
Minimum Viable Management
Product, design and engineering rarely agree and that’s a good thing. In this episode, Mike McQuaid and Neha Batra break down what healthy tension actually looks like, why alignment is overrated and how leaders can turn disagreement into better outcomes.
18 December 2025
I’ve been following what Justin Searls has been doing with his blog for some time. He’s been leaning into the “POSSE” (Publish on your Own Site, Syndicate Elsewhere) philosophy more and more. In practice, this looks like building your own version of a single-serving social network on your own site and exposing RSS/Atom feeds to other services to consume. Justin recently released POSSE Party which makes this easier by cross-posting to various social networks. I’ve complained for a while about (anti)social networking so I’m always up for new ways to use social networking less.
09 December 2025
The process of software estimation is frustrating for software engineers and those who consume their estimates. Consumers often ask “why can these software engineers not just tell me when it will be done?”.
14 November 2025
Minimum Viable Management
Mike and Neha explore how leaders can recognise when things are going wrong, why admitting mistakes builds trust, how to spot low psychological safety, and the value of written plans, accountability and steady course correction when guiding teams through tough moments.
31 October 2025
Minimum Viable Management
Mike McQuaid and Neha Batra break down how leaders spark momentum and keep it steady. They start with clarity of mission, ruthless scope cuts, and visible wins in weeks not years. They cover simple not easy systems that reduce drag, like milestone slices, anti-goals, handoffs that follow the sun, and temporary process as guardrails you later remove. They show why constraints breed creativity, how to automate recurring pain, and why teams should target low volatility over peak velocity. They close with saying no, letting the right fires burn, and building a candid culture through trust and social capital.
24 October 2025
In tech, 3 years is often considered a “long tenure”. We maintain open-source projects for 2 years, then burn out. We start habits, lose momentum and quit.
23 October 2025
Minimum Viable Management
How can teams feel safe to speak up while still hearing hard truths? In this episode of Minimum Viable Management, Mike McQuaid and Neha Batra explore what it really means to balance psychological safety with direct, honest communication. They discuss the practical work of rebuilding trust in teams, the role of consistency and humility in leadership, and how to make openness a habit, even when conversations are uncomfortable.
They also touch on remote work, written communication, and when individual contributors should share their opinions in decision-making. A candid look at how safety and honesty can, and must, coexist for teams to thrive.