When I tell people I have 10 thumbs when it comes to anything technical, they don't believe me. In fact, they point to all the articles and blog posts I've written about using the command line to try to refute my claim.
I'm no expert or wizard with the command line. Far from that. And I'm not one of those people who believes that you absolutely must be fluent in command line/shell/terminal (or whatever you want to call it) to be able to use Linux. I know any number of folks who happily and productively use Linux. Not one of them have ever cracked open a terminal window.
So why do I write about the command line, especially in posts and articles aimed at those without many (or any) technical skills? Aimed at people like me? Two reasons.
Second, you don't need to be an expert to use the command line. You don't need to know how to script. You don't need to remember ever option for every tool that you use. You only need to remember the options that you need to remember, nothing more.
Yes, anyone can use the command line.
That said, being able to use the command line isn't a requirement for using Linux. But using it can expand what you can do with Linux.
Information. We all deal with more than a bit of it daily. Notes, links, ideas, tasks, quotes, snippets, and interesting files. And how we deal with those pieces of information varies from person to person. Some of us store them in text or word processor files. Others use one or more online tools. Some of us even use reliable, old fashioned paper.
But no matter how you collect your information, managing it is always a chore. And while there are a number of open source tools for effectively managing your information, why not turn to the command line? One excellent command line tool for managing information is pygmynote.
If you're doing any work at the command line, that work probably involves more than a couple of keystrokes. You can save time and reduce the amount you type at the command line in two ways.
One way is to create a script that encapsulates all of the commands and options that you'll be using to perform an operation. All you need to do is run the script along with, say, a file name. That's great for single or multiple commands that require a lot of options.
For other commands, an easier way is to create an alias. An alias replaces the command and its options with something shorter. For example, if you want to list the contents of a directory in detail, you can type ls -l at the command line. Or, you can create the alias ll and use that instead.
Many people believe that getting organized involves a calendar, a todo list, or some arcane and complex mix of software. That's one way to do the deed. It's effective, but it's not the most efficient way of doing things.
Instead, why not put everything under one roof? Or, in this case, into a single terminal window. How? By using a dashboard.
System administrators, DevOps engineers, and developers use dashboards to keep on top of what they need to keep on top of. Dashboards do that by breaking information into discrete chunks and displaying those chunks in their own spaces on screen. All that information is available at a glance and it's easy to understand.
A dashboard isn't just for the techie. Even if you have 10 thumbs when it comes to things technical, you can benefit from using a dashboard. I'm one of those folks with 10 thumbs, and I find dashboards to be very useful.
While I'm not a fan of its name, I am definitely a fan of what WTF does and how it does it. And that's display a lot of different information in a way that's clear and easy to follow.