Zero to Terminal

Lab Progress 0/5 completed

From “I’ve never used a terminal” to “I deployed a website using nothing but the command line”

Who Is This Track For?

This track is for absolute beginners. You don’t need any IT background, any coding experience, or any special knowledge. If you can use a web browser, you can do this.

Maybe you’re:

A student curious about technology
Someone switching careers into tech
A non-technical person who wants to understand what developers do
Someone who’s been told “just open a terminal” and felt lost

You are welcome here. Every expert was once a beginner.

What You’ll Learn

By the end of this track, you’ll be able to:

Understand what’s happening inside your computer (and why it matters)
Use the terminal (command line) to navigate, create, and manage files
Edit files using a text editor right in the terminal
Understand networking, servers, and how to connect to them remotely
Know what “the cloud” actually means (spoiler: it’s not magic)
Deploy a real website using nothing but the terminal

This track leads to two paths: Linux Deep Dive (systems internals) and Cloud Native (containers, Kubernetes). Most senior engineers know both.

The Restaurant Kitchen Analogy

Throughout these modules, we use a restaurant kitchen as our running analogy:

Computer Concept	Kitchen Equivalent
CPU	The chef (does the work)
RAM	Counter space (temporary workspace)
Disk/SSD	The pantry (permanent storage)
Operating System	The restaurant manager
Programs	Recipes
Terminal	Talking directly to the kitchen staff
Server	A restaurant kitchen (serves many customers)
Cloud	Renting a commercial kitchen instead of building your own

This analogy will carry you all the way from here to Kubernetes, where you’ll manage thousands of kitchens automatically.

Modules

Module	Title	Time	What You’ll Learn
0.1	What is a Computer?	20 min	CPU, RAM, disk, OS — the kitchen hardware
0.2	What is a Terminal?	20 min	Opening and understanding the terminal
0.3	First Terminal Commands	25 min	Navigate, create, move, and delete files
0.4	Files and Directories	25 min	Paths, file types, organizing your filesystem
0.5	Editing Files	25 min	Edit files with nano, write your first script
0.6	Git Basics — Track Your Work	45 min	Track your work with Git — init, add, commit, log
0.7	What is Networking?	25 min	IPs, ports, DNS — how computers talk to each other
0.8	Servers and SSH	25 min	What servers are, how to connect remotely
0.9	Software and Packages	25 min	Installing and managing software from the terminal
0.10	What is the Cloud?	20 min	Cloud computing, AWS/Azure/GCP, where K8s fits
0.11	Your First Server — Putting It All Together	45 min	Capstone: deploy a real website using everything you’ve learned

How to Use This Track

Go in order. Each module builds on the last.
Do the exercises. Reading is not learning. Doing is learning.
It’s okay to be slow. Speed comes with practice, not pressure.
Re-read if needed. Professional engineers re-read documentation constantly.
Take breaks. Your brain needs time to absorb new concepts.

What’s Next?

After completing Zero to Terminal, the road forks into two paths:

Path A: Linux Deep Dive

You loved the terminal? Go deeper into how Linux actually works — the kernel, processes, networking internals, permissions, and security. This is the knowledge that makes you dangerous.

Start here: Linux Fundamentals

Path B: Cloud Native

You want to build and deploy apps at scale? Learn containers, Docker, and Kubernetes. This is where the industry is heading.

Start here: Cloud Native 101

Path C: Both

Most senior engineers know both. Start with whichever excites you more — the other path will be here when you’re ready. Both paths converge at Platform Engineering (SRE, GitOps, DevSecOps, MLOps).

               Zero to Terminal
                     |
              Module 0.11 (Capstone)
                     |
          +----------+----------+
          |                     |
     Linux Deep Dive      Cloud Native 101
          |                     |
          +----------+----------+
                     |
            Platform Engineering

Time Investment

Total track time: ~4.5 hours

That’s it. A few hours from “I’ve never used a terminal” to “I deployed a website on the internet.” Not bad for a weekend.

Remember: The tech industry needs people with fresh perspectives. Your beginner eyes see things that experts have become blind to. You’re not behind — you’re just getting started.