Understanding the TerminalđŸ’»

Hello, Queens of tech! 👑 Today, we’re diving into a super cool tool that every developer needs to know—the Terminal. Don’t worry if you’ve never heard of it or think it’s too “techy.” By the end of this post, you’ll feel like a Terminal Queen! ✹

What is the Terminal?

The Terminal is like a magic wand for your computer. It lets you talk directly to your Operating System (OS) by typing commands instead of clicking buttons. Think of it as texting your computer to make it do things!

💡
Check out my article on Operating System(OS) if you haven’t yet for better understanding.

Why Should You Use the Terminal?

  • It’s powerful: You can do tasks faster than using the mouse and menus.

  • It’s essential for coding: Installing tools, running programs, and testing your code often happens here.

  • It’s fun: Once you get the hang of it, you’ll feel like a hacker in a movie. đŸ•¶ïžđŸ’»

How to Open the Terminal

Opening the Terminal depends on your OS. Since we’re focusing on Linux here, let’s start with that:

For Linux Users

  1. Shortcut: Press Ctrl + Alt + T on your keyboard.

  2. From the menu:

    • Look for an app called Terminal or Console in your applications menu.

    • Click it, and voilà—the Terminal window opens!

*This is my Terminal, powered by Garuda Linux and the fish shell. 🐟 It might look advanced, but don’t worry—you’re on your way to creating your own epic setup too! Just keep coding! đŸ”„

What Does the Terminal Look Like?

  • It’s usually a black or white window with a blinking cursor, waiting for you to type something.

  • Don’t be intimidated—it’s not judging you; it’s just patiently waiting! 😊

A Simple Terminal Command

Let’s explore a basic command to check your Windows version. Follow these steps:

Step 1: Open the Command Prompt

We are going to move our mouse pointer to the bottom left of the screen as seen in the picture and click on the windows button Type cmd and press Enter. This opens the Command Prompt.

Step 2: Type the Command

Type the following command into the Command Prompt:

“systeminfo”

(Exactly as shown, no changes.)

Step 3: Press Enter

After typing the command, press Enter on your keyboard. You’ll see detailed system information, including your Windows version

Let’s try a basic command to check your Linux version. Follow these steps:

Step 1: Open the Terminal

Use the shortcut (Ctrl + Alt + T) or find it in the menu as explained above.

Step 2: Type the Command

Type the following in the Terminal:

uname -a

(Don’t worry about what it means yet—just type it exactly as shown.)

Step 3: Press Enter

Hit Enter on your keyboard, and you’ll see something like this:

Linux my-computer 5.15.0-79-generic #86~20.04.1-Ubuntu SMP Fri Jul 7 15:04:22 UTC 2023 x86_64 GNU/Linux

Breaking It Down

  • Linux: This tells you that your OS is Linux.

  • 5.15.0-79-generic: This is the version of the Linux kernel (basically, the engine running your OS).

  • Ubuntu: This is the Linux distribution (distro) you’re using.

Why Should You Learn the Terminal?

  • It’s a universal tool: Almost every developer uses it, no matter the programming language or framework.

  • You’ll need it to:

    • Install tools like Node.js and VS Code (Read my article on Setting Up Your Coding Wonderland đŸ› ïž

    • Run commands for your projects.

    • Debug your code like a pro.

Fun Analogy

Think of the Terminal as a secret diary where you can write commands to your computer, and it listens! But instead of keeping secrets, it helps you get things done faster.

Pro Tips for Beginners

  1. Don’t panic: If something doesn’t work, check what you typed. The Terminal is case-sensitive!

    What Does "Case-Sensitive" Mean?

    Being case-sensitive means that the Terminal treats uppercase (capital) letters and lowercase (small) letters as completely different characters.

    For example:

    • File.txt is not the same as file.txt.

    • myCommand is not the same as MyCommand or MYCOMMAND.

Why Does This Matter?

When you type commands in the Terminal, they need to match exactly—right down to the capitalization. If you type something like:

    Ls

instead of:

    ls

You’ll get an error because the Terminal doesn’t recognize Ls as a valid command.

How to Avoid Case-Sensitive Errors

  1. Pay attention to capitalization: Always double-check what you type.

  2. Copy-paste when in doubt: If you’re following a tutorial, copy the commands to avoid typos.

  3. Learn the common commands: Over time, commands like ls, cd, and mkdir will become second nature to you.

Quick Analogy

Think of case sensitivity like entering a password:

  • If your password is Hello123 and you type hello123, it won’t work because the uppercase "H" is different from the lowercase "h."

In the same way, the Terminal is picky about the exact spelling and capitalization of commands and filenames.

💡
So, next time something doesn’t work, don’t panic—just check for a sneaky uppercase or lowercase mix-up! 😉
  1. Use Tab: If you’re typing a long file or folder name, press the Tab key to autocomplete it.

  2. Ask for help: Type man <command> (e.g., man uname) to get a manual explaining what a command does.


Homework

  1. Open your Terminal and try the uname -a command.

  2. Screenshot your results and share them with your learning group or community.

  3. Look up one more Terminal command to try—start exploring!


The Terminal may look scary at first (It felt that way for me too), but once you start using it, you’ll realize it’s your coding BFF. Stay curious, and let’s unlock more magic together in this journey! 🚀

💡
Got questions? Drop them in the comments or reach out—I’m here to help!
30
Subscribe to my newsletter

Read articles from Joy Tari-Bagshaw directly inside your inbox. Subscribe to the newsletter, and don't miss out.

Written by

Joy Tari-Bagshaw
Joy Tari-Bagshaw

Hey there! I’m Joy Tari-Bagshaw, a passionate software developer with 3+ years of experience and a deep love for teaching and learning. As the first female Google Developers Student Club Lead at my university, I’ve mentored countless beginners, facilitated bootcamps, and helped aspiring developers land their first tech roles.After teaching at several bootcamps, I’ve realized the urgent need for this blog. The limited time frame of most programs often doesn’t allow for in-depth learning, and I wanted to create a space that simplifies complex topics while giving beginners the time and resources they need to truly grasp them.Every day, I get messages from people asking for advice on how to start or grow in tech. That’s why I’m on a mission to make web development simple and accessible for everyone through my blog series, Build, Break, Debug, Repeat. Whether you’re a total newbie or leveling up your skills, I’m here to guide you with resources, tutorials, and a sprinkle of humor along the way.Let’s build something amazing together!