In my experience, systems admins tend to be the most familiar and comfortable on the shell, though even there, mileage varies markedly. Devs can vary a lot, I find skills rare among UI / design types, even those (most nowadays) using Macs, and for administrative / project management types, it's often very little. Based largely on casual observation, mind.
The other point is that specificity of knowledge can very greatly, and IT is all about specialization. Even people who are good at multiple tools often have their limits, and I'll see specialization in development, databases, networking, build/release management, QA, systems development (as opposed to app or UI work), and related specialties such as networking and others. Specific skillsets too are often accidents of opportunity and history -- having moved through a specific shop or acquired a particular skill is very much dependent on where you've been, much less a mark of innate ability.
One recent team I worked with had access to a set of highly complementary talents: very strong systems knowledge, database, overall app and enterprise architecture, and a networking consultant. Resolving a number of issues and enhancements turned out to rely very much on each individual's strengths, where what any given member could provide by way of easily accomplished tasks (seconds or less) would have set the rest of the team hours or days.
What I find particularly damaging is environments in which expertise is guarded while at the same time begrudging others for what they didn't know (and not providing for knowledge transfer) generally leads to negative engagements. This is almost always present in part (nobody knows everything or has time to teach everyone), but in particular cases has been a very strong undercurrent.
A post like that would also make HN front page if the presentation or premise were attractive enough. See http://learnxinyminutes.com/ which has been featured here multiple times, including once for its Python docs https://news.ycombinator.com/item?id=5959502 with 149 points.
We simply like that stuff. There's always someone who doesn't know, or something you missed.
The irony is I remember when people gave me shit for running OS X back in 2001 and being "stupid for not running windows" and "making my life harder". The schadenfreude of a Windows user watching me when something didn't just work automatically or I had to boot up VirtualPC back then was far from subtle and peppered with reminders I could "just run windows dude". Now days, it's still there, but it's much more common and much stronger coming from a Mac user than any Windows users I've encountered as of late.
9/10 times when I'm using a command that isn't part of my "daily list" I'll need to consult man pages and/or Google.
I've used xargs hundreds of times, but depending on when I used it last, I can never remember if I need -0 or not, and is it $1 or {} or wait, no no, I'm using awk, so it's $1, and I need to changes something... is it needle, haystack, replacement or... hell, I'm not even sure if it's substr or just sub... errrr.
Not to mention some of these are distro specific, in some you use service name start, in others it's /etc/init.d/service start. Some it's adduser, others it's useradd, etc. It's relative to the distro a lot of the times... are the files in /usr/opt/ or /opt/... or maybe they're in /usr/local/opt/... Also they list stuff like locate, but not updatedb. Not a single mention of dd or shred or /etc/resolv.conf or netcat (I fucking love netcat!) or unzip (far more likely to need to unzip an archive than add a user in your day to day life).
We're not command libraries, we're duct tape mechanics.
edit: if you're interested in learning more... I honestly can't recommend this book enough.
http://www.amazon.com/Linux-System-Administration-Handbook-E...
I love that xkcd. I really hope someone will take up the task of replacing the UI of *nix with something better. For me, it's like Windows 8: it was a nice idea to combine touch and traditional user interface - it just turns out to be inferior to either being done well. Writing shell scripts is just, let's face it, horrible, and the command line interface far from ideal. It works, it has for decades. But it's not like there has been a lot of competition to compare with.
Sibling is complaining about academia and universities - but again, apart from sys admins, who don't teach, none of the academics know this stuff. Learning and teaching Python (Java) is in some respect easier but more importantly interesting - it just doesn't make sense to learn all these commands without actually needing them (whoever comes up with an exercise to use them all together gets a medal).
Now days it annoys me if a library doesn't have a CLI. Even on my personal machines I run the least amount of GUI possible for resource and usability purposes. I don't want a new GUI or a better CLI (zsh, csh, bash, ksh, etc. do just fine). I just want tools that utilize it properly to support it's most powerful functionality (pipes, output redirect, proper exit codes, etc.)
A lack of familiarity with it is no institutes fault, it's a personal fault, if you find your self looking at a CLI interface, and then resorting to searching Google for a GUI wrapper for that interface, the ignorance isn't due to a failure of the CLI, it's a failure of the user being intimidated or ignorant.
Also I have no issues writing shell scripts, I use them all the time to save me tons of work. If you're a programmer then you really get to know your system and you really get to customize it to your liking.
An example would be switching to i3 from Gnome/KDE. I was a long time KDE/Gnome/XFCE user and my laptops track pad settings would never stick after a reboot when I used the GUI tools for disabling the touchpad tap to click or just disabling it in general (thinkpad nipples ftw). After moving to i3 and really getting more access to the core of the system I ended writing a couple little shell scripts for enabling disabling my touchpad for when I need/want it. What used to be a 5 step operation (open gui > click tab > uncheck box > click save) has now become (super+space, type disa[tab](autocomplete disable.touchpad), enter). I have a second script to enable it again, the contents of which are small.
#!/bin/bash
exec synclient TouchpadOff=1
There are all sorts of issues with altering the nix toolset, and we mustn't forget the importance of POSIX for compatibility. We can't simply decide to 'replace the UI of *nix' without fundamentally changing how the nix ecosystem and community operate (and I wouldn't want to). OS development is not agile and rarely compat breaking, and for good reason.
I also read the sibling as promoting a fundamental understanding of the underlying platform being developed on, not so much pushing teaching of just CLI usage. Knowing how, e.g., the filesystem works and the caveats involved is something that can lead to much better software design decisions. And knowing how to chain a cheap sed instead of just throwing Python and the re module at a glob.glob listing can be just as useful.
I find my job wearing a DevOps hat to be very often much more difficult than it ought to be because so many programmers clearly don't understand the OS layer they're running on (both when supporting internal developers at various places which I've called $work, and using OSS and commercial software in that role)
There's no shame in running `man xargs` to get the syntax just right (we're not dictionaries) but general knowledge of what those tools are and how to use them are _essential_ to being a good developer... this is an essence too often neglected by universities and professionals.
That was my point.
I don't really think so. You can get by fine developing a lot of things without knowing linux tools. They are helpful, though. What if you're working on Windows like a ton of devs do?
If you find yourself using xargs frequently, you should check out GNU Parallel https://www.gnu.org/software/parallel/
a seperate issue : if you're going to make lists like this, please don't include distribution specific commands (like yum or apt-get) on 'linux' cheatsheets. they belong on redhat or ubuntu cheatsheets, respectively.
Similarly irritating : the use of distribution specific package names.
There are a lot of tasks which one ought to be familiar with which aren't anywhere near cross platform, and keeping your list to very widely available tools will leave huge gaps in your knowledge and makes for rather short lists.
That said: some of the commands I use most often are exceptionally basic. And in the case of others, I'm learning things all the time. Say, such as mplayer's constant-pitch video playback speed argument: