DEV Community

Cover image for My Linux Course Put Me to Sleep, So I Built Something That Wouldn’t
Maame Afua A. P. Fordjour
Maame Afua A. P. Fordjour Community Curator

Posted on Edited on

My Linux Course Put Me to Sleep, So I Built Something That Wouldn’t

Features a built-in terminal and XP system

Confession time. I signed up for the free Introduction to Linux course from the Linux Foundation. It's a really good course. It's thorough, it's free, and it covers everything you need.

But a few chapters in, my brain checked out.

Page after page of reading. Then more reading. I'd read about cd and mkdir, nod along, close the tab, and forget all of it by the next morning. If you've read my post on why I stopped watching tutorials and started breaking things, you know this is my weak spot. I don't learn by reading. I learn by doing, breaking and fixing.

So I built the kind of Linux learning experience I actually wanted: short, hands-on, and fun.

👉 Try it here: https://pixel-linux-quest.vercel.app

The Linux Compass, but levelled up

Back in January I built The Linux Compass for the GitHub Copilot CLI Challenge. It was a terminal tool that fought what I called "knowledge decay": you'd look up a command, it explained it, and it saved everything to a study log so you wouldn't forget it.

It helped. But honestly, it still felt like homework.

Pixel Linux Quest is the upgrade. Instead of logging what you learned, you learn it by doing. You read a tiny lesson, then you prove it straight away in a real (pretend) terminal in your browser, then you earn XP and unlock the next topic. All wrapped in a retro pixel art style, because learning should be fun.

What's inside

  • A story intro. Pip, a little pixel penguin, tells you how Linux came about, from Unix in 1969 to a student in Helsinki in 1991, in 7 animated pixel scenes.
  • Bite-sized lessons. Each level is a tiny lesson, then a quick check. Some are quizzes, most are hands-on terminal tasks.
  • A pocket terminal in your browser. Nothing to install. It even has Tab completion and Ctrl+C, like the real thing.
  • A live folder map. Type mkdir treasure and a folder pops up on a pixel map. Type cd treasure and Pip walks there. This is the part I wish I had when I first learned Linux, because I could never picture where I was.
  • Pip explains your mistakes. You still see the real Linux error, but Pip adds a friendly note. Type cd Treasure and Pip says "Close! Linux cares about capital letters."
  • The Break It sandbox 💥 Every beginner wonders what happens if you type rm -rf /. Now you can find out safely. Fun fact I learned while building this: modern Linux actually refuses rm -rf / with a built-in safety check. You have to try a bit harder to destroy everything. The sandbox shows you both. (There's a secret badge if you manage it.)
  • A Break Room 🕹️ I get distracted easily, so I added a little pixel arcade with three retro mini games for 5 minute breaks. After 20 minutes of learning, Pip asks if you want a break, then sends you straight back to where you left off.

This is just the beginning

This is an ongoing project, and it's going to keep growing.

Right now the first two sections are live: Linux basics and your first commands (8 levels so far). Over the coming weeks I'll be adding:

  • New topics every week: files and permissions, processes, text tools and pipes, and Bash scripting.
  • Real-world missions: things like "the website is down, find the error in the logs".
  • A challenge at the end of each section that mixes everything you learned.
  • More break room games, including a calm one for when you just need to chill.

I'll be sharing updates here as it grows, so follow along if you want to see where it goes.

How I built it

I treated it like a real product, not a weekend hack:

  • Design first. I started with a mockup of the screens and a written brief with the rules: the colours, the fonts, the lesson format, and "every Linux fact must be correct".
  • Small phases. I built it in stages and tested each one before moving on.
  • Saying no. The first intro scenes were just coloured boxes. I hated them, so they got redone in proper pixel art.
  • Fact checking. A learning site that teaches wrong things is worse than no site, so every lesson gets checked against how real Linux behaves.

The stack: React, Vite and TypeScript. The terminal is a small Linux-like shell written in TypeScript with a pretend filesystem. There are 322 automated tests, GitHub Actions runs the tests and the build on every push, and it's hosted on Vercel.

The DevOps student in me is very happy about that CI pipeline. 😅

I need your help

This is the first version, and I want real feedback to shape what comes next.

  1. Try the first two sections and tell me where you got stuck, bored or confused.
  2. Try to break Linux in the sandbox and post your SYSTEM DESTROYED screenshot in the comments.
  3. Spot a wrong fact? Please tell me. I'd rather be corrected than teach something wrong.

It's open source, so you can also contribute: new lessons, new break room games, fixes, anything.

⭐ GitHub: https://github.com/Maame-codes/pixel-linux-quest

If you're learning Linux too, or you got bored of your course like I did, give it a go and let me know what you think. 🐧

Curriculum topics inspired by the free Introduction to Linux (LFS101) course. Not affiliated with or endorsed by the Linux Foundation.

Top comments (13)

Collapse
 
csm18 profile image
csm •

Really good app for beginners! Especially the file system traversal,
the command and the location where we are in the tree is side by side!

Collapse
 
maame-codes profile image
Maame Afua A. P. Fordjour •

Thank you, that’s the exact part I was most excited about! When I was learning, I could never picture where I was after a few cd commands, so seeing the map move next to the terminal was the thing I wanted most.

Next week the map gets busier, with files, permissions and moving things around. If there’s anything you’d like to see added, I’m all ears. And thanks for completing all the levels !!

Collapse
 
csm18 profile image
csm •

One thing I personally regret is with the destructive commands like rm -rf.
If when learning we are warned that what that command will do, we get that habit of being careful.

Thread Thread
 
maame-codes profile image
Maame Afua A. P. Fordjour •

That’s such a good point, and honestly the reason the sandbox exists. Reading “be careful with rm” never stuck for me. Watching everything disappear did.

The update I’m finishing today takes it further. In the new File Forest world, there’s a clean-up mission where you have to delete junk files without touching the important ones, and if you remove the wrong file, the level fails and you start again. The lesson before it also teaches one habit I wish someone had told me earlier: run ls with the same path first, so you see exactly what rm is about to delete.

Thread Thread
 
csm18 profile image
csm •

Reading “be careful with rm” never stuck for me. Watching everything disappear did.

I totally agree! Until we see we messed up, we don't get that fear that will teach the lesson.

The points you mentioned are real needed ones. Would love to play the next levels!

And thank you so much for the gem!

Thread Thread
 
maame-codes profile image
Maame Afua A. P. Fordjour •

Will keep you updated and No p :)

Collapse
 
the_4th_life profile image
Diego •

the break room after 20 minutes is a smart touch, and having pip send you straight back to where you left off takes away the "where was i" moment after a break. is the 20 minute mark fixed, or can people set their own length?

Collapse
 
maame-codes profile image
Maame Afua A. P. Fordjour •

Thanks Diego! That “where was I” moment was exactly what I wanted to get rid of. Breaks only help if coming back is easy.

Right now the 20 minutes is fixed, but you can switch the nudges off completely with the gear icon in the top corner. Your question made me realise it should be more flexible, so I’m fixing that this week. You’ll be able to pick your own interval, and when a break ends you’ll get a real choice: stay a bit longer or jump back in. No more being rushed out after one extra two minutes. It’s your break, so you should decide how long it lasts.

Collapse
 
wbcomdesigns profile image
Wbcom Designs 💡 •

The "close the tab and forget it by morning" problem is exactly why short do-then-explain loops work better than reading chapters. One thing that might help it stick even more: bring back a command from a few levels ago inside a new challenge, so learners have to recall it rather than recognise it. Do you track which commands people get wrong most? That list would be a great guide for what to resurface.

Collapse
 
maame-codes profile image
Maame Afua A. P. Fordjour •

This is such a good point, and you’ve named exactly the problem I had. Recognising a command when you see it and recalling it from a blank prompt are two very different skills.

To answer your question: not yet. Right now everything stays in the learner’s own browser and I don’t track anything, which I like for privacy. But knowing which commands trip people up most would be really useful, so I’m thinking about a simple, anonymous count of failed commands, with no accounts and no personal data.

Your recall idea fits perfectly with what’s coming. Each world is getting a final challenge that mixes everything from earlier levels, and I’m going to take it a step further from your comment: older commands will come back in later levels without a hint, so you have to remember them. Thanks for this, it’s going on the list.

Collapse
 
gautamtalksdev profile image
Gautam K •

Building the thing that would have kept you awake is the best kind of course review. Learning Linux by fixing something broken sticks far better than reading about commands.

Collapse
 
maame-codes profile image
Maame Afua A. P. Fordjour •

“The best kind of course review” might be my favourite way anyone has described this project. Thank you!

You’re so right about fixing broken things. That’s why the sandbox lets you destroy everything: you learn a lot more about what rm -rf does when you watch it happen than when you read a warning about it. Next on my list is missions where something is already broken and you have to fix it, like a website that’s down and logs to dig through.

Some comments may only be visible to logged-in visitors. Sign in to view all comments.