Unix Basics It Pays To Know
When writing about digital technology, or any topic, is something you do, it takes time to accumulate credibility. Even if you put in the study time up front to know your stuff, building trust takes time.
I’ve been fortunate that, after years expanding my portfolio and the knowledge base under it, people come to me for advice on related subject matter. I’m still not totally comfortable in this position, but I roll with it.
As more professionals put stock in my technical background, I have been exposed to more specialized technical environments and use cases. Friends asking for consumer electronics troubleshooting is worlds apart from professionals looking to overcome a technical hurdle.
This new class of advice I’m prompted to provide has elucidated the challenges that professionals confront. Moreover, when I field the same question multiple times, it hints at a potential gap in computer science training. Naturally, I want to do my part to close it.
To be clear, I’m not putting anyone down. There are plenty of things I don’t know and probably should. I simply want to draw attention to concepts that I’m surprised that competent individuals struggle with. Specifically, what I regard as key Unix principles I’ve found notably missing.
I’m not totally surprised, as a lot of “tech sector” professionals work in levels of abstraction above the OS. But it pays to know these Unix basics considering there is often a Unix/Unix-like OS somewhere in the abstraction hierarchy. If that layer is unsound, the whole edifice risks collapse.
To that end, I want to highlight questions I’ve been asked about Unixy (my substitute for “Unix and Unix-like”) systems, and the fundamentals to grasp to become self-sufficient.