On the value of tools that reward investment with understanding, not just output.
Looking back, the most valuable skills I possess share a common origin: they began with a choice to engage with a system deeply, rather than merely consume its output. My journey with bodywork started not with seeking a quick fix, but with studying shiatsu—learning the meridians and the principles of pressure to understand my own health. My relationship with transportation transformed when I learned bicycle mechanics, not just to save money, but to know every component that carried me through the city. This pattern of choosing the path of understanding over convenience found its ultimate expression in my choice, years ago, to build my digital life on Linux and open source. That choice, often met with bemusement, has proven to be less about software preference and more about cultivating a fundamental literacy.
Unlike the opaque systems that dominate our lives, these pursuits share a philosophy: they are tools that teach. They reward curiosity with capability and replace dependency with a quiet, enduring form of sovereignty.

Understanding a complex system, whether a city or software, begins with seeing how its parts connect.
The initial motivation for each of these pursuits was practical. Shiatsu offered a framework for self-care. Learning bike repair promised independence from costly shop visits. Linux presented a way to use a powerful computer without the financial and procedural friction of proprietary licenses. Yet in each case, the superficial goal was quickly eclipsed by a deeper reward: the cultivation of a working understanding.
Engaging with a system on its own terms changes your relationship to it. You stop seeing it as a magic box that either works or doesn’t. You begin to see architecture, cause and effect, and points of leverage. Fixing a slipping gear teaches you about tensile strength and precise alignment. Tracing a network issue on a Linux server teaches you about packets, protocols, and logical pathways. The knowledge gained is not just procedural; it is architectural. It grants you a map of the territory, which is the first step toward true agency.
This form of learning has a particular texture. It is often slow, sometimes frustrating, and fundamentally antidotal to the instant gratification of consumer technology. Its value compounds silently, revealing itself not in a flash, but in the accumulated confidence of knowing you can diagnose, repair, and adapt.
The modern software landscape is largely built on a proposition of managed ignorance. Proprietary platforms are designed to be used, not understood. Their interfaces guide you toward approved actions while deliberately obscuring the underlying machinery. Updates are deployed, features are added or removed, and business models shift—all with the user in the role of a passenger, not a pilot. The transaction is simple: you surrender agency for the promise of seamless convenience.

Mastery begins with the details—understanding each component’s role in the whole.
Linux and the open source philosophy present a different proposition entirely. The initial cost of entry is a willingness to look under the hood. The command line, configuration files, and package management are not barriers to be hidden, but interfaces to be learned. This transparency is the core of the value. When your system behaves unexpectedly, you are not left to hope for a fix in the next opaque update; you have the tools and the right to investigate. You can read the logs, examine the configuration, and often, understand precisely why.
This model cultivates a specific kind of intellect: the problem-solving mindset of an engineer or a mechanic, not just the consumption habits of an end-user. It teaches you to think in systems, to trace dependencies, and to appreciate elegant solutions. The skill it builds is not merely “how to use Linux,” but “how to understand how complex systems operate and fail.” This is a form of literacy that transfers far beyond the terminal window.
The investment in this literacy pays dividends across three interconnected domains: capability, economy, and autonomy.
The capability gained is foundational. Navigating a Linux system builds a mental model of computing that makes you more effective with any technology. Concepts like file permissions, process management, and networking cease to be abstractions. This depth of understanding makes you a better troubleshooter, a more informed buyer of technology, and less susceptible to the jargon and gatekeeping that often surround technical domains. It turns you from a consumer of digital products into a participant in a digital environment.
Economically, the model is one of ownership over rental. The shift of proprietary software to universal subscription models is a shift from purchasing tools to paying perpetual rent for access. Open source inverts this. The software is a commons. You invest your time in learning it, and in return, you own your toolkit outright. The financial savings on licenses—for operating systems, office suites, creative software, and development tools—are significant and recurring. But more importantly, you escape the cycle of planned obsolescence and forced upgrades. Your system evolves at your pace, according to your needs, not a vendor’s quarterly targets.

The quiet sovereignty of repair and maintenance, applied to both physical and digital machines.
This leads to the ultimate dividend: autonomy, or digital sovereignty. Your system, your data, and your workflow are not subject to the commercial or political whims of a distant corporation. There is no telemetry you cannot disable, no feature removal you cannot circumvent, no license server that can revoke your access. This sovereignty is not primarily about hiding; it’s about control. It’s the assurance that your critical tools cannot be altered or taken away because a board of directors decided to pivot. In a world where our digital and real lives are inextricably linked, this control is a profound form of freedom.
The old critique that open source demands sacrifice—of polish, compatibility, or ease—has largely crumbled. The ecosystem has matured into a compelling offering on its own terms. Modern Linux desktop environments rival or exceed their proprietary counterparts in stability and design. Tools like LibreOffice and OnlyOffice handle the vast majority of document work with flawless compatibility. Creative professionals have powerful, viable alternatives in software like Krita for painting and Kdenlive for video editing.
Even in gaming, the last bastion of Windows dominance, the landscape has transformed. Initiatives like Valve’s Steam Deck have demonstrated that high-performance gaming on Linux is not only possible but often superior, driving an industry-wide effort to ensure compatibility. The argument for the proprietary platform based on necessity has evaporated.
Choosing a tool that teaches is, in the end, an ethical and practical stance. It is a rejection of the learned helplessness that commercial technology often cultivates. Just as understanding basic nutrition empowers you to make better food choices, and understanding mechanics empowers you to maintain your vehicle, understanding the fundamentals of your digital environment empowers you to navigate the modern world with greater security and intention.
The person who only knows how to click “Update” or “Subscribe” is at a permanent disadvantage to the person who can ask “how” and “why.” In an age of algorithmic influence, data extraction, and rapid technological change, this disadvantage is not merely technical—it is civic and personal.
My shiatsu training taught me to listen to my body’s signals. My bike repair taught me to maintain what I depend on. Linux taught me to navigate and command the digital substrate of contemporary life. These are not separate skills; they are expressions of the same principle: that the deepest form of security and freedom comes not from relying on black boxes, but from cultivating the understanding to open them.

The reward of deep understanding: a clear view of the landscape and the ability to navigate it on your own terms.
On Tool Literacy and Sovereignty
This essay reframes the choice of Linux and open source software as part of a broader philosophy of engaging deeply with tools. It argues that systems which are transparent and demand understanding—like shiatsu, bicycle mechanics, and open source software—provide compounding returns in capability, economic efficiency, and personal autonomy. This stands in contrast to opaque, consumption-oriented models that trade convenience for user dependency and control. The mature, capable state of the open source ecosystem today validates this approach as both a practical and principled path forward.