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 !!
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.
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.
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?
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.
One team, one community stack for WordPress: BuddyNext, Reign, BuddyX, Jetonomy, Learnomy & more. Custom community, LMS and marketplace builds. 13+ years.
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.
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.
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.
“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.
We're a place where coders share, stay up-to-date and grow their careers.
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!
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 !!
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.
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.
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!
Will keep you updated and No p :)
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?
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.
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.
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.
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.
“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.