It's hard to give advice without knowing what you do, and why you want to learn to use the terminal... But: Learn about the command line tools that exist, and

It's hard to give advice without knowing what you do, and why you want to learn to use the terminal... But: Learn about the command line tools that exist, and actually use the ones that match what you regularly do. Take small steps, first move a file from the command line. Then, compile your stuff, launch an application. Then use git to commit, pull, push, drop changes. Then learn more git, cherry pick, interactive rebase, stash, diff. If something feels tedious, and you think "there must be a better way", take a moment to Google if there is a better way. Even if you might not save time (for the first time) , give it a try, and see how long it takes to solve something new. Make your terminal yours and a joy to use. It might just be me, but I like when my terminal looks and feels great. Don't make learning an overwhelming experience. It's a marathon, so if on the beginning, you only learn 2-3 tools, that's okay, you'll learn the others when you need them. I picked up Vim (Helix) and tmux only years after I was proficient on the command line. It's okay to forget stuff... When I worked on the backend, I was good at grep, log tools, etc, but today, I need some time to get things working. Watch videos about other people's set up, it's great inspiration on what's possible. Write your own tools, learn what makes an intuitive interface, learn to handle different kinds of flags, arguments. Learn to type. Practice typing faster. Learn "terminal adjacent" skills. Learn how to navigate your OS with the keyboard (close tabs, windows, search, lock the screen, launch an app). Don't be afraid to "toss things out". Some tools are just trash, some tools just don't click for you. If it hurts, stop doing it. If the tool is actually good, you'll hear about it later, at which point, you can give it another go.