During our first week at NIAT, mentors had us switch our primary development environment to Linux (or WSL2 on Windows). For anyone accustomed to double-clicking desktop icons and dragging files around in Windows Explorer, working exclusively in a bash shell initially feels slow and intimidating. But once the core commands become muscle memory, you realize how much faster a terminal-centric workflow is.
Here are the terminal commands and habits that transformed our daily productivity: using grep -rn and ripgrep to search through thousands of codebase lines in milliseconds; piping outputs with awk and sed for text wrangling; monitoring system CPU and memory leaks with htop during heavy model training; and using tmux to keep remote server sessions alive over SSH without disconnecting.
Another game-changer was configuring zsh with autojump (z) and fzf fuzzy search. Instead of clicking through ten nested project directories, typing z capstone jumps straight into the working tree. When you deploy servers on AWS EC2 or GCP Compute Engine later in your course, there is no graphical user interface—it's just a black terminal window and a bash prompt. Learning to feel completely at home in the command line early on is an indispensable superpower for any software engineer.
Edited