In my experience repetition helped. Not memorization, but more like muscle memory.

Also, ensuring to never copy and paste commands but to type them in manually yourself. It’s hard to enforce this on yourself, but worth it.

I appreciate that this article started with “ways to reduce risk” because that’s an extremely valid concern and tied to why you shouldn’t ever copy and paste. The one time in my early Linux forays where I copied and pasted I wiped the wrong drive. It definitely taught me to always manually type it in and not get too lazy, because what you copied might not match what you want to do exactly.

2 things got me comfortable on command line: 1) A great cheat sheet (one from Ubuntu: https://ubuntu.com/download/server/thank-you); 2) Practice all the commands from the cheat list regularly. Last page is something for Pro version, but first 2 pages are great for a begginer. There is a typo at a command (or it was in a past cheat sheet): “Sudo change <username>” instead of “sudo chage <username>”. It helped me most to get comfortable with terminal. Enjoy!

tl;dr: Gradual exposure over time.

I got used to it through work, as I had to ssh into a server to run simulations. That mainly involved navigating the file system and text editing (which I used vim for) to make some basic Python and bash scripts, including sed and awk. The latter two I never got comfortable using, and haven’t really touched since.

I was using macOS at the time, and after using that for work, the terminal in macOS got at first less scary and then a preferred way of accomplishing certain tasks. On my work Windows computer I started missing having a proper terminal around, and I eventually found Cygwin and later Git Bash to give me that terminal fix in Windows as well. Especially with the latter I noticed few differences and could use it to a large extent as I would have on my then Macbook.

2-3 years ago I was in need of a new computer, and at that point a laptop with Linux on it was not a very scary prospect. That is by no way saying I went into Linux as an expert, far from it, and I am still very much a newbie - but opening the terminal to work with things is not at all a barrier, which helps a lot if you use Linux and want to be able to do some changes from the defaults. If you don’t want that, I think you can go far these days without opening the terminal, but it is certainly a good skill to have.

Stumbled across a game that teaches the command line as you play it. Seems like a good place to share https://gitlab.com/slackermedia/bashcrawl

personally, writing and saving simple scripts - IE project based learning - is how i got time in the saddle.

I have no clue… I grew up on Windows 3.11 and I thought Windows was kinda lame while MS-DOS was the coolest thing ever because you typed things like magic spells 😅

Step 1: Use a youtube tutorial for the basic commands. Don’t worry, you’ll forget about them soon enough. But doing them once, helps with muscle memory.

Step 2: When in need to do something, copy/paste from Q&A/forums various commands that they suggest for your problem. Your basic knowledge from step1 will come back as you do that.

After a few days, you’ll be understanding what’s going on and how the whole thing works in an abstract level.

if the avg enduser has to temper in a commandline, your program is ass.

/

to search man pages was a gamechanger

Virtual environment? Taking notes of what they did?

Anyway, tell them it’s okay you experiment and mess things up. Show them how to backup their important work. Then walk them through inevitably having to reinstall their distro.

They’ll learn that you can just keep moving forward, fixing and learning as you go.

Using computers since before GUI was available… Sometimes I think we ought to go back to it

When you aren’t in a rush try to do stuff in command instead, looking for a file? , try to find it in command. Need to copy and move a folder? Don’t use your file manager, use the command line instead.

Eventually you will piece together the bits you learn and it starts to make sense, and then you feel like a God. Lol.

The need to do it plus the realization that you can script anything based on it.

Drivers. Using recovery mode. Administration. Wanting to describe what to do rather then manually do it. Wild cards are really powerful and so is find and xargs. The text processing commands are useful too.

The other thing is having started computing in the 1970s. Everything was command line back then. GUI systems only become universal in about 1995.

For me it was self hosting, aka not having a choice but to learn. I’ll be dead before using remote desktop for that.

Also, self hosting gives you real motivation, because you actually need to do things, carry tasks, not just learning for the sake of it. Your efforts get immediately rewarded with functioning things.

Practice.

Mastering the command line? A few observations. First, consult and take notes (yes, even seasoned terminal veterans forget syntax.) Secondly, embrace tab completion. It’s your friend, and a surprisingly effective substitute for remembering every single command. Third, the true test: procure a VPS or remote server and exclusively use the command line. No GUI crutches allowed. It’s a digital wilderness, and you’ll learn to navigate it.

Lastly, and this is non-negotiable: keep a terminal window permanently resident on your desktop. Consider it a vital organ, deserving of its space. It’s a constant reminder of the power you wield, and a readily available portal to a world beyond the pretty buttons.