It took me twenty years to make Linux my daily driver. Not because I didn’t want to. Because every time I tried, something stopped me. A missing driver, a configuration file I couldn’t decode, a game I wanted to play, some piece of software my livelihood depended on that only ran on Windows. I would install, struggle, reach the limit of my patience, and reformat back to safety.
Until this year.
The Weekend Install Loop
I discovered Linux when I was in high school. Slackware, Red Hat, and SuSE. I did not understand what I was doing, but I understood that it mattered. There was something about an operating system you could configure yourself, piece together yourself, break yourself.
I stayed over at a friend’s house and brought my computer with me. The whole thing. Tower, monitor, keyboard, mouse. We would install Linux in different flavors all weekend, splitting our attention across two machines, leaving one working so we could use dial-up to find documentation that barely existed. We did not know how to exit vi. We could not get things working. But we had books, we had time, and for reasons I still cannot fully articulate, we would just reinstall Linux over and over. Different distros. Failing to configure X. Celebrating when we could switch between virtual terminals and X Windows and Enlightenment.
XBill and some bubble-popping game were it for entertainment. I played a couple of MUDs that an upperclassman showed me in Speech class. He was super cool in my eyes. He played Master of Puppets in that class too. But I could never stay on Linux for long. Everything I did was on Microsoft Windows. There was always one thing or another I needed Windows for.
The Decade of Near Misses
When I started working on computers, my first internship was on a Macintosh. Now that was an alien system compared to anything else I had used. MS-DOS, Windows 95, Windows 98. I skipped Windows ME thankfully, and then Windows 2000. When I learned about virtual machines in one of my first real jobs, I installed Linux again, and Solaris this time as well. I have never met Solaris in the wild. Linux lasted a few days, maybe a week at most, before I reformatted back to Windows.
I did not understand what a man page was. I had secondhand books. I would go back to Windows, where a vibrant pirate ecosystem supported all manner of exploration. I learned how to use all the tools my employers would eventually pay for.
Years went by and I got another taste of Unix when macOS switched to a Unix foundation. I never understood the architecture, but I liked having it under the floorboards. When I went back to Windows, I missed it. Mac still had most of my software, but not everything. I stuck to Windows. I kept Linux as an idle curiosity, usually in a virtual machine. Safe. Isolated. Temporary.
Each attempt got a little less romantic. I knew the wall by then.
What Changed
I tried Linux again this year because Windows let me down.
I had a stable Windows setup. It worked. I trusted it. Then something happened that eroded that trust. Nothing dramatic in isolation, but enough small failures, enough uncertainty about whether the next update would break something, enough sense that the system I had built my workflow around was no longer reliably on my side. I looked at my laptop and realized I did not want to replace it yet. It was still good hardware. The hardware was fine. It was the software relationship that had soured.
Linux was the extreme departure I needed. Somewhere different enough that I could not fall back into the same patterns. I did not expect it to work out. I had failed at this too many times. But I was frustrated enough that failure felt better than staying put.
So I installed it as my main operating system. I wiped the drive and committed. I half-expected to reformat within the week.
I thought there would have been more changes, but the landscape was nearly the same. More package managers, more software, more drivers, and the same old configuration headaches. Audio devices that would not route properly. Touch screens that needed specific kernel parameters. Backlight controls buried in sysfs. GPU configurations that fell apart after an update. All the familiar failure modes, waiting.
What changed is that I had local LLMs and CLI agents sitting next to me while I configured the machine. Opencode became my wingbot. I would hit a problem, describe it in plain language, get a precise fix or a debugging strategy, apply it, and move on. The wall I had hit for two decades was a feedback loop wall. I finally had a way across it.
I still reinstalled three or four times in the first week. Some of it was impatience. Some of it was genuinely broken configurations I could have avoided. But I have been full-time Linux on my personal laptop for nearly three months now, and that is the longest I have ever stayed on a Linux machine. The important change was not that the machine stopped having problems. The problems stopped being dead ends.
I have not stopped using Windows entirely. It is still on other computers I own and interact with regularly. But Windows is no longer on my main personal machine. That machine is Linux, and I am not waiting for the excuse to go back.
Fun, Finally
Here is the part I did not expect: it became fun.
Actual fun. The kind of fun I had in high school installing Slackware on a Saturday morning, before the failures stacked high enough to drain the enjoyment out of it. Now the fun does not stop when something breaks. I describe the failure, get a diagnosis, apply the fix, and go back to whatever I was doing.
Linux stopped being a project I was perpetually failing at and became a system I actually used. I installed things because I wanted to try them. I configured services because I was curious. I started looking forward to tinkering instead of quietly bracing for the next subsystem to bite me.
Usefulness followed naturally. Once I stopped fighting the OS, I could put it to work. I set up a local AI stack. I automated backups. I learned actual system administration because I wanted to, not because some broken package had dragged me into the basement by the ankle.
The strange part is how normal it feels now.
Audio routes across Bluetooth and HDMI. The touch screen works. The keyboard backlight works. GPU switching works. Sleep and wake work. Printing works, which still feels like asking too much from any operating system. The old crisis list became ordinary machine behavior.
Opencode turned the broken parts into conversations instead of research projects. I could read a debug log without drowning in it, apply a configuration change, and keep moving. Linux did not get simple. The feedback loop got short enough for me to stay.
The thing that kept me coming back all those years was the sense that Linux was serious business in a way Windows never was. Grey beard programming. System administration. The kind of professional competence I did not have but wanted to earn. Even when I could not get it working, I knew the capability was there, behind a wall of arcane knowledge I did not possess.
After these long years, my goals have changed. I still respect and revere the people who came before me, the ones who learned the hard way because there was no softer path available. I also do not need to perform suffering as proof that I belong here. I can get my work done and learn the system as I go.
I am just using the computer with Linux now. That is the part I wanted all along.
LLM Disclosure: This post was written with AI assistance for drafting and style refinement.