I Trapped Myself in Arch Linux for 365 Days. Here's Why I’m Never Leaving.
I built Ferryman to solve a simple problem: manual cross-posting is low-leverage work that drains your time. With 10,500+ posts ferried for 380+ users, the system is proven to help you grow on all your socials with zero extra effort. Start scaling your reach automatically. Use code “BREAKSTUFF” for 30 days free of the Creator plan.
Over a year ago, I bought an old Thinkpad with the sole intention of messing around. I wanted to upgrade the hardware, tinker with the internals, and see if I could daily-drive Arch Linux.
What started as a weekend hobby turned into a year-long obsession that has fundamentally rewired how I interact with computers. Most people see Arch as a digital “Choose Your Own Adventure” that ends in frustration, but after 365 days, I’ve realized it’s the ultimate productivity hack.
Here is what a year of daily driving Arch Linux aught me about engineering and peace of mind.
1. Tinkering is the Best Teacher
We often forget that computing is supposed to be fun. Picking up that Thinkpad and upgrading the RAM, swapping the SSD, and rice-ing the UI rekindled a curiosity I hadn’t felt in years.
Installing Arch forces you to understand the layers of the stack. You aren’t just clicking “Install”; you’re partitioning disks, managing the kernel, and configuring display protocols. You learn more about how a computer actually works in one week of Arch than in three years of using MacOS. The interest in how things work is the engine of a great engineering career.
2. Configuration is Freedom (and Efficiency)
Most operating systems ship as a “one-size-fits-all” product. Arch, on the other hand, is a blank canvas.
Through my configuration, I’ve removed everything that doesn’t serve me and optimized everything that does. My machine is now a 1-of-1 system designed specifically for my brain. Because the environment is a joy to use, I actually want to be at my desk more. When your tools are an exact extension of your workflow, you don’t just work faster; you also work with more intent.
3. Use What You Deploy On
99% of us are deploying our code to Linux servers. Yet, a massive portion of the industry develops on MacOS or Windows.
Using Linux as a daily driver gives you a deep, intuitive understanding of the environment your code actually lives in. When you understand systemd, permissions, and package management at the OS level, you become a far more effective engineer. You stop treating the server as a mystery box and start treating it as familiar territory.
4. The Peace of Mind: Cattle, Not Pets
Perhaps the biggest shift has been moving to a “Cattle, Not Pets” philosophy for my hardware. For most people, their laptop is a “pet”: if it breaks or gets stolen, their life stops for three days while they try to recover data and settings.
I’ve optimized my setup for total reproducibility:
Dotfiles: Every configuration is version-controlled via GNU Stow.
Setup Scripts: I can reproduce my setup on a brand-new machine in under 10 minutes.
Remote Devevelopment: All my actual coding happens on a persistent machine in the cloud via SSH.
Syncthing: My files are constantly mirrored across all my relevant devices.
This means my laptop is now just a “thin client” and a portal into my work. Whether I’m on my Framework laptop running Arch, my MacBook Pro, or my Windows desktop, I pick up exactly where I left off. If my laptop breaks today, I don’t care. Nothing is lost.
Where you can find me online:
Drop a like ❤️ and comment below if you made it to the end of the article.