In 2025 I did something that sounds like a personality change and felt like reclaiming my tools: I transitioned off Windows and Mac as daily drivers and went all-in on Arch Linux.
Not because I wanted a hobby OS. Because I was tired of my machine disagreeing with production.
The dual-OS tax I did not notice until it was gone
For years the pattern was familiar:
- Mac for “nice” local UI work and meetings
- Windows for the occasional vendor tool, Office reality, or game night that turned into “I will just finish this ticket here”
- Docker and SSH as the duct tape between those worlds and Linux servers
That tax shows up as tiny lies:
- path separators and line endings that only break in CI
- Node versions that “work on my Mac”
- VPN / cert / filesystem case-sensitivity surprises
- performance theater where fans scream while a container builds
Arch did not magically remove complexity. It removed the fake comfort that my laptop was a different planet from Linux production.
Why Arch, specifically
I wanted:
- rolling currency without waiting for a vendor to bless a package
- explicitness: I install what I use, I understand what broke
- a system close enough to server Linux that Docker, systemd habits, and networking intuition transfer
- a machine I could tune instead of negotiate with
Arch’s reputation is “you will break it.” The real reputation should be “you will learn why it broke.” For an engineer who leads teams through AWS and container deploys, that learning loop is not masochism. It is reps.
The fun parts (yes, fun)
There is joy in a machine that feels like yours:
- a tiling workflow that stops the window-shuffling circus
- a terminal that is not a second-class citizen
- pacman + AUR as a honest package conversation
- customizing the desktop without five layers of “enterprise defaults”
- watching build times and Docker I/O stop feeling haunted
I will not pretend the first week was spa-like. The first week was me arguing with mirrors, GPUs, and my own past assumptions. Then one morning everything was quiet and fast, and I realized I had been paying a UI tax for years.
The benefits that actually changed work
Closer to production
Most of what I ship lands on Linux. Developing on Arch made local failure modes rhyme with remote failure modes. Fewer “works on my Mac” postmortems. More “the container and the host agree.”
Better Docker muscle memory
Volumes, networking, cgroups, and resource limits stopped being abstract slides. They became daily physics. When a teammate’s container was slow on Mac file sharing and fine on Linux, I could explain it without folklore.
Cleaner teaching
When I mentor, I can say “this is what the server sees” and mean it. Pairing on Linux hosts, CI runners, and local Arch boxes shares one mental model.
Ownership over mystery
Windows Update and macOS “we moved your cheese” moments train helplessness. Arch trains ownership. Ownership is a leadership trait as much as an OS preference.
What I tell people who ask if they should switch
Do not switch for aesthetics alone. Switch if:
- your production is Linux
- you want fewer environment lies
- you are willing to read logs instead of reboot-blaming
- you like improving your tools as part of craft
Keep a recovery path. Dual boot or a spare machine for the first month is wisdom, not weakness.
Leadership takeaway
The Arch move was personal, and it was professional. Leaders who never feel the grain of their tools eventually manage abstractions they cannot debug. Getting closer to Linux made me faster at shipping and clearer at teaching.
Also, yes: neofetch still hits different.