Where Habit Meets Understanding

Mon, 28 Sep 2026 04:36:15 +0000

Last week I told you about Chapters 1-3. This week I moved on to Chapters 4-6.

The terminal is not new to me, but going back to the fundamentals on purpose is teaching me things I'd been doing on autopilot 😂

Let me take you through how the week went.

It Started With Open Source

I've heard "open source" a million times and nodded like I fully understood. This week I finally got into what it really means: the code is out there for anyone to read, use, change and share.

Then the acronyms arrived 😭 GPL, copyleft, FOSS, FSF, OSI, Creative Commons. My brain was like, "Sis, all of this in one chapter?"

What helped was slowing down and asking what each one is for:

FOSS is free and open source software
GPL is a license that keeps software free, even after people modify it
Copyleft is the idea behind that: if you build on free software, you keep it free
FSF and OSI are the organisations that push and define all of this
Creative Commons does a similar job for creative work like writing, images and music

Tip: Don't memorise acronyms. Understand the purpose and the names will stick on their own.

Then Came the Command Line

I did the labs and typed everything out myself instead of just reading, and chale, going back to basics on purpose hits different. Some of these commands I use often, but this time I actually looked at what each one does:

echo      # displays text or values
history   # shows commands you've used before
type      # tells you what kind of command something is
which     # shows where a command lives
man       # opens the manual for a command

Tip: history is underrated. It's a record of everything you've tried, mistakes included 😂

Chapter 6 Taught Me What Matters Most

This chapter reminded me of something every good hacker knows: you don't have to know everything, you just need to know how to find help.

Here's the toolkit:

man ls      # read the manual for a command
whatis      # quick one-line description
man -k      # search manuals by keyword
apropos     # same idea as man -k
whereis     # find a command and its documentation
locate      # find files and directories
info        # more detailed documentation
--help      # quick help straight from the terminal

Tip: Before you open Google, try --help or man first. It trains you to find answers on your own, and that's a real skill.

The Part That's Still Hard

The vocabulary. Sometimes I'm reading and I stop like, "Wait, what does this one mean again?" 😭

But I'm learning not to rush. I read, practice, get confused, check the documentation, try again, and somewhere in that loop it starts to click.

What I'm Taking Away

Linux isn't about memorizing every command. It's about understanding what you're doing and knowing how to find your way when you don't know something.

That's a lesson that goes beyond Linux, honestly.