Disclosure: This post includes affiliate links; I may receive compensation if you purchase products or services from the different links provided in this article.
Have you ever been amazed to see someone working very fast in UNIX terminal, firing commands, and doing things quickly?
Yes, I have seen that a couple of times, and It has always inspired me inspired to learn from those superstar developers.
In this article, or tutorial, or whatever you call it, I have shared some UNIX command practices I follow to work fast, quick, productive, or efficiently in Linux.
I work for Financial services industry, and my work involves development and support of online stock and futures trading application in Electronic trading, Derivatives, FX, Commodity, and other asset classes.
All our services run on Linux servers so it's essential for us to work efficiently and quickly in a Linux terminal and that's how I have learned these productivity tips in Linux.
If you have not read those, you can see if you find them interesting and useful. In this UNIX command tutorial, I am going to share my experience on how to work quick, fast, and efficiently in UNIX.
If your server also resides in a Linux machine and your day 2-day work involves a lot of searching and playing around UNIX commands then these tips will save a lot of your time.
Below tips are the result of my years of experience in UNIX terminal which I have summarized as 10 tips to work fast in UNIX.
Why I am sharing this?
Well, I love these kinds of productivity tips, which is easy to learn and remember but makes a huge difference in your day-to-day work. By sharing this, I am looking forward is to get some more tips from you guys to enhance my arsenal so please share how you work in UNIX, how you make most of powerful Linux commands and shell utilities provided by Linux and other UNIX operating systems like Fedora, Ubuntu, CentOS, etc.
Please share your experience by posting comments to make this post useful and get most of it and benefit from each other's expertise.
Anyway, let's start with these useful tips:
This has saved me 30% time on average. It always happens that you fire same UNIX command multiple times within a fraction of seconds,
before knowing this trick I used to use up and down arrow for finding my power and then executing them which takes a lot of my time, but, after knowing this trick, I just have to just remember the command name like
!ls will execute your last
"ls -lrt" ,
!vim will open your final file without typing full command.
Use this tip and experience it, It definitely saves loads of time, and it's also useful on shell other than bash shell (like
ksh) where up and down arrow generally doesn't give you previous commands.
For example, After doing ls -l stocks.txt if you want to open stocks.txt, you can use the vim editor as vi !$ (last argument).
This is the extension of the previous tip, which is used to execute the very last command you have completed. Since it just involves two keystrokes and that too for the same key, it's amazingly fast.
This will also work on the shells in which up and down arrow doesn't work like K shell and C shell. This is extremely useful if you are stopping or starting your server or Java application for debugging ging purpose frequently.
Btw, if you are not familiar with bash shell yet, I suggest you take a look at Bash Shell Scripting: Crash Course For Beginners, which will teach you the bash shell from the command line to shell script.
A very useful course for someone who wants to become a power user in Linux.
Best out of the lot if you remember your last command executed sometime back and just want to find that command with the same argument and execute.
This is the tip you need to remember.
Just press the
"CRTL+R"and type words that you had in your last command and UNIX will find that command for you then just press enter.
All the above three tips will save a lot of your time if you execute commands frequently, and percentage of repetition is quite high. for me
I have saved almost 50--60% time by following the above three tips. Let me know how it works for you guys.
Well, this was the first tip I learned when I started working on UNIX. This is your most helpful command in UNIX and Shell scripting.
In most of the cases, there is a certain command like starting, stopping, checking log files, making a build or doing release, etc.
These are the commands you often need to execute and if you don't remember exact command no need to worry, just do
history | grep "keyword" and you will get that command from the history on your Linux machine.
There are certain environment variable, e.g. HISTSIZE which defines how many command UNIX history can store, so have it big
Enough to save your time and avoid referencing your command booklet every now and then.
Btw, if you are not familiar with basic Linux commands, then I suggest you go through Shell Scripting: Discover How to Automate Command Line Tasks to get yourself familiar with commands like this.
It will save you tons of your time by avoiding Google every now and then to search appropriate Linux commands for the task at hand.
The grep and find are the two best tools UNIX provide to us. Almost everybody needs to search something in UNIX, e.g. a file, a directory, certain words in a file, e.g. ERROR or Exception and if you know how to use the grep and find with regular expression you will save a lot of your time by typing fewer commands.
For example, by knowing about
egrepyou can fire
egrep "ERROR|Exception" *.xmlinstead of firing two grep command for finding ERROR and Exception individually.
I have shared a lot of useful options for these two commands on those articles, which will help you to get more from these two powerful Linux commands.
As shown above this nice little tip I guess everybody knows.
If you don't, it's better to start with a nice Linux course like Linux Command Line Basics, as you might not know some other fundamentals as well.
From my personal experience, joining a nice course is better than finding essential information in bits and pieces.
And, if you don't mind learning from FREE resources, you can also check out my list of 5 FREE Linux courses for developers.
Have you seen some strange commands working in someone's machine and not yours, which might be aliased he would have set up in either his
Always do such kind of setup for commonly used command. There are lots of usage of the .bashrc and .profile file, but one of the most important ones is setting up aliases, e.g., "l." which finds all hidden files. "ls" which includes all useful option, e.g.
-lrtH to show all relevant information.
You can further see Linux Command Line Interface (CLI) Fundamentalsto learn more about how login works in Linux and what is the role of
.bashrc files in Linux and bash shell.
Btw, you would need a Pluralsight membership to access this course, which costs around $29 monthly or $299 annually (14% saving). I have one, and I also suggest all developers have that plan because Pluralsight is like NetFlix for Software developers.
It has more than 5000+ good quality courses on all the latest topics. Since we programmers have to learn new things every day, an investment of $299 USD is not bad at all.
Btw, it also offers a 10-day free trial without any obligation which allows you to watch 200 minutes of content. You can watch this course for free by signing for that trial.
Based on my experience, navigation in UNIX shell takes almost 50% times of people and if you are going to write directory path every now and then just forget about working fast.
So, instead of typing full name use all the above tips and make the best use of pushd, popd, cd --- and cd ~ command. cd --- is best if your switching between two directory location in UNIX.
The less you type, the faster you work.
To make use of your last typed command, make use of tab in bash, so that let the UNIX bash shell complete your command.
Use Ctrl+R if the last command you have typed is very long and you want to change just a few lines.
Try to learn more commands and their options and use this will reduce thinking the time for a particular task and use ctrl+z and fg and bg to suspend a process.
It saves almost 10% time if you are viewing multiple files or log files so instead of every now and then executing vim commands just do
Ctrl+Zto suspend it and fg 1 or fg 2 to bring it in the foreground.
I hope these examples, tips on UNIX command will help you to do more in less time and enhance your productivity and experience while working in UNIX.
And if you are looking for some resources then you can check out Learn Linux in 5 Days and Level Up Your Career
This list is by no means complete so please share how you are working in UNIX and of course how fast are you working in UNIX?
5 Free Linux Courses for Programmers
Linux Command Line Interface (CLI) Fundamentals
How Linux Works: What Every Superuser Should Know
10 examples of curl command in Linux
10 examples of lsof command in Linux
Top 10 Python Courses to learn Coding in 2019
Learn Linux in 5 Days and Level Up Your Career
Shell Scripting: Discover How to Automate Command Line Tasks
Linux Administration Bootcamp: Go from Beginner to Advanced
Thanks for reading this article so far. You might be thinking that these are very stuff and there is no point learning them, but you will be amazed how much time you will save by applying these tips in your work.
There is a good chance that you may already know most of the stuff, and there are also a lot of useful free resources which you can use, I have also linked them here and there along with best resources, which are certainly not free, but totally worth of money.
I particularly like Udemy courses as they are very affordable and provide a lot of values in very small amount, but you are free to choose the course you want.
At the end of the day, you should have enough knowledge and experience about the essential Linux commands and bash tricks.
Good luck with your Linux journey! It's certainly not going to be easy, but by following these tips, you will save a lot of time and become the Linux superuser you always wanted to be.
P.S. --- If you just want to start with one course to learn Linux, I think the Linux Command Line Basics is the best one to start with.