<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
<channel>
<title>Coder Legion - Recent posts tagged -learning-growth</title>
<link>https://coderlegion.com/tag/-learning-growth</link>
<description>Powered by Question2Answer</description>
<item>
<title>Linux in Practice: Files, Directories and Archives — Chapters 7-9</title>
<link>https://coderlegion.com/29927/linux-in-practice-files-directories-and-archives-chapters-7-9</link>
<description>&lt;p&gt;Last week I continued my Linux Essentials revision, working through Chapters 7-9. If the first two weeks were about reconnecting with the system from the outside in, this week was about going back over the things I use daily, files, directories, archives, and actually sitting with the reasoning behind habits I've had for years.&lt;br&gt;
Here's how the week unfolded.&lt;br&gt;
Chapter 7: Revisiting Where Things Belong&lt;br&gt;
I've navigated a filesystem for years, but this chapter asked a question I'd stopped asking a long time ago: why do things live where they live?&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Went back over how Linux organises files and directories, and the logic behind that structure&lt;/li&gt;
&lt;li&gt;Re-grounded myself in key directories: /home, /etc, /tmp, /usr, /var&lt;/li&gt;
&lt;li&gt;Practiced pwd, cd, and ls with intention again, instead of on autopilot&lt;/li&gt;
&lt;li&gt;Revisited the difference between absolute and relative paths, properly this time&lt;/li&gt;
&lt;li&gt;Reviewed the shortcuts I use without thinking: . (here), .. (one up), ~ (home)&lt;/li&gt;
&lt;li&gt;Went back to reading ls -l output closely and spotting hidden files, instead of scrolling past them&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Tip: &lt;code&gt;/etc&lt;/code&gt; holds configuration, &lt;code&gt;/var&lt;/code&gt; is where things change over time, like logs and caches. Revisiting that distinction alone makes troubleshooting someone else's system far less intimidating.&lt;br&gt;
Chapter 8: Re-earning My Respect for rm&lt;br&gt;
This chapter covered commands I already use often, but I made a point of slowing down and sitting with what each one actually does, instead of relying on muscle memory.&lt;br&gt;
Wildcards and globbing first:&lt;/p&gt;
&lt;pre&gt;&lt;code class=&quot;language-bash&quot;&gt;*    # matches anything
?    # matches one character
[ ]  # matches a set of characters

&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Then the fundamentals, revisited properly:&lt;/p&gt;
&lt;pre&gt;&lt;code class=&quot;language-bash&quot;&gt;cp       # copy
mv       # move / rename
touch    # create a file
rm       # remove a file
mkdir    # create a directory
rmdir    # remove an empty directory

&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Tip: &lt;code&gt;rmdir&lt;/code&gt; only removes empty directories. A small detail, but it's Linux quietly protecting you from yourself.&lt;br&gt;
Chapter 9: The Revision I'd Been Looking Forward To&lt;br&gt;
Archiving and compression. This chapter finally untangled a distinction I'd been blurring for years without realising it: archiving bundles files together, compression shrinks them. Two different jobs, often performed together, but never quite the same thing.&lt;br&gt;
I also went back over lossless versus lossy compression, lossless preserves every bit, lossy trades some quality for a smaller file size.&lt;br&gt;
I practiced with:&lt;/p&gt;
&lt;pre&gt;&lt;code class=&quot;language-bash&quot;&gt;gzip / gunzip     # compress / decompress
tar               # create, list, extract archives
zip / unzip       # work with ZIP files

&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;And the &lt;code&gt;tar&lt;/code&gt; options genuinely worth remembering:&lt;/p&gt;
&lt;pre&gt;&lt;code class=&quot;language-bash&quot;&gt;-c    # create
-t    # list
-x    # extract
-f    # specify the archive file
-z    # gzip compression
-j    # bzip2 compression
-v    # verbose output

&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Tip: &lt;code&gt;tar -czvf archive.tar.gz folder/&lt;/code&gt; is essentially the one line worth memorising from this entire chapter.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;What This Revision Taught Me&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This block of chapters felt different from the first two weeks. Less &quot;what does this word even mean,&quot; and more &quot;I already know this, I'm just understanding it properly for the first time.&quot; Organising a project folder, archiving it cleanly, navigating a system with purpose rather than habit, it's a reminder that revision isn't just repetition, it's where the real understanding actually settles in.&lt;br&gt;
Chapters 10 and beyond, coming soon.&lt;/p&gt;
&lt;p&gt;The Duchess of Hackers&lt;br&gt;
Full-Stack Developer | Digital Marketer | Cybersecurity Enthusiast&lt;/p&gt;
</description>
<category>Articles</category>
<guid isPermaLink="true">https://coderlegion.com/29927/linux-in-practice-files-directories-and-archives-chapters-7-9</guid>
<pubDate>Tue, 06 Oct 2026 03:00:24 +0000</pubDate>
</item>
</channel>
</rss>