0 / 15 lessons — 0%
Lesson 15 / 15 ✅
Best practices & real-world patterns
The habits that separate "I got it working" from "it keeps working without me watching it."
- Automate anything you type more than twice — a shell script or Ansible role beats tribal knowledge in someone's head.
- Monitor disk space proactively — a full disk breaks logging, databases, and package installs all at once, and it's entirely preventable.
- Centralize logs off the box itself when you can — a server that's down can't be SSH'd into to read its own logs.
- Patch on a schedule, don't wait for an incident to remind you a box is months behind.
- Document non-obvious manual steps the moment you do them — "why is this configured this way" is always harder to answer six months later.
- Test backups by actually restoring from one occasionally — an untested backup is a hope, not a plan.
- Prefer configuration management (hello, Ansible) over hand-tuned snowflake servers — a server nobody can safely rebuild from scratch is a liability.
- Know your rescue/recovery plan before you need it — practicing a recovery once, calmly, beats improvising one during an actual outage.
The "it's fine, I'll remember" trap. The manual fix applied under pressure at 2am, never written down, is exactly the fix that gets re-discovered the hard way six months later by someone else — possibly you.
You made it. Filesystem to boot process, permissions to performance triage — that's the operating system every course before this one has actually been running on top of. Take the quiz, then CI/CD is next: the automation that turns all of this into something that happens on every commit, not just when someone remembers to run it.