About This Guide

A 30-day terminal learning path built by someone who's learning right alongside you.

Why I Built This

I switched to Linux because I wanted to understand how things actually work. But when I got started, I realized I needed to learn the basics first — the terminal, file systems, how commands work.

Most guides either assume you already know everything or throw you into the deep end. I needed something in between — a structured path that builds confidence step by step.

So I built this guide. It's the learning path I wish I had. Every lesson is designed to teach you one concept at a time, with safe practice in a folder you can delete if anything goes wrong.

The Teaching Philosophy

Safe by Default

Every command in this guide runs inside ~/linux-practice — a sandbox directory you can delete in one second if something goes wrong.

Real Commands, Not Toys

You'll learn the actual tools Linux professionals use daily: grep, awk,find, sed. Not simplified examples.

Explanations First

Every command comes with a plain-English breakdown of what each flag does and why you'd use it. No "just copy this" — you'll understand what you're typing.

Who This Is For

•Windows or macOS users who want to understand Linux without dual-booting or setting up a VM
•Developers who've been avoiding the terminal and want to stop feeling like they're missing out
•Complete beginners who've never opened a command line and don't know what PATH or $HOME means
•People switching to Linux who want a structured path instead of "figure it out as you go"

How to Use This Guide

1.Start with Day 1. The lessons build on each other. Skipping ahead will leave gaps in your understanding.
2.Do the practice exercises. Reading isn't enough. Type every command, see the output, break things (safely), and fix them.
3.Use the Command Reference. When you forget what grep -i does, look it up. The reference is there for the long term.
4.Ask questions. If a lesson doesn't make sense, that's a bug in the guide, not in you. Try re-reading the previous days or search the command reference for more context.