Terminal tutorials, tested.
Every command you see in a ShellProven video was run in a fresh Debian container first. The output on screen is the real one. The commands are published so you can check them yourself.
# Files changed in the last 24 hours — the trap is -mtime 1 vs -mtime -1
$ find . -type f -mtime -1
./src/app.py
./src/config.yaml
./logs/app.log
$ find . -type f -mtime 1 # "exactly one day old" — not what you wanted
./src/utils.py
How it works
Three rules, every lesson.
Run first, show second
Each command is executed in a clean container and the recorded output is what you see. If it doesn't work, it doesn't ship.
Commands you can copy
Every lesson has a folder in the public terminal-tutorials repository: the commands, a setup script and the real log.
Quick check
Two short questions at the end of each video, with the answer a few seconds later. Try them here on the lesson page, too.
Lessons
Linux command line and bash — short, practical, with the traps called out.
Find files changed in the last 24 hours (and the -mtime +1 trap)
find, -mtime vs -mmin, -newermt, pruning node_modules
Search a whole project with grep -r, without node_modules, .git or binary junk
grep -r, --exclude-dir, -I, -n and friends
Undo anything in Git: restore vs reset vs revert (live demos)
Which one to use, and which one rewrites history
Linux file permissions: read ls -l, fix "Permission denied", and never chmod 777
rwx, octal, chmod, chown — and the safe defaults
SQLite in the terminal: query a CSV file in 5 minutes (and the text-number trap)
.import, .mode, CAST and why your numbers sort wrong
Bash redirection explained: >, >>, 2>, 2>&1 and | (and why the order matters)
stdout, stderr, pipes — with the order trap demonstrated
Disk full? Find what's eating your space with df, du and sort (Linux)
df -h, du -sh, sort -h, deleted-but-open files
SSH keys from scratch: generate, install, shortcut with ~/.ssh/config, turn off passwords
ssh-keygen, ssh-copy-id, config aliases, sshd hardening
Cron job not running? It works in the terminal, here's why it fails in cron
PATH, environment, percent signs, logging the output
awk for people who hate awk: 8 one-liners that answer real questions about a log
fields, filters, counting, sums — nothing more
tar and gzip without the usual mistakes: back up a folder, skip the junk, verify the archive
tar -czf, --exclude, tar -tzf, extracting to the right place
rsync instead of cp: copy only what changed, dry-run first, and the trailing-slash trap
rsync -a, --dry-run, --delete, and the trailing slash
Transparency. The script and the narration are made with AI and reviewed by a human before publishing. The robot presenter and the dog are AI-generated cartoon characters — not real people. What is not generated: the commands and their output, which come from real runs in a container.