Build the concepts behind practical infrastructure engineering work.
Four short guides, each with a plain-English explanation, a precise figure, and a matching question to answer in Foundations. About six minutes each. No profile needed to read; a free profile keeps your practice.
One useful sequence, not an endless library.
Read them in this order. Each guide ends with the practice that matches it and the next guide.
Then What DNS actually does explains the first thing that happens before any connection, and the first thing to check when a healthy service cannot be reached.
Choose the concept you need next.
Why engineers live in the terminal
What the terminal is, why professionals choose it, and how a typed command becomes an answer you can read, repeat and share.
Read the guide →Search inside files with grep
Turn a huge log into the few lines that matter, with a source-and-output comparison and a compact flag reference.
Read the guide →Watch a log with tail -f
Follow new log lines as they arrive, see a cause and its effect side by side, and carry the habit into containers and clusters.
Read the guide →What DNS actually does
How a remembered name becomes a machine address, why a cached answer differs from a fresh one, and what to check when a healthy service cannot be reached.
Read the guide →Practise in Foundations
Make a decision, commit to it and get feedback written for that decision. Free profile, no card or installation.
Start FoundationsUse the 90-day roadmap
Place these guides inside a structured twelve-week infrastructure engineering sequence.
See the 90-day roadmap