Master the version control system every engineering team depends on — the three-state model, branching strategies, rewriting history, collaboration workflows, and the commands behind each.

Become fluent in the Unix command line — the shell, filesystem navigation, pipes, redirection, process control, permissions, and text-processing tools that glue every other systems skill together.

A practical orientation to the languages systems engineers actually write — C's closeness to the machine, Rust's memory safety, and Go's concurrency — and when to reach for each.

Learn the editing and search workflows that turn raw files into maintainable systems — from fast navigation to refactoring with regular expressions.

Understand what happens between source code and a running binary — compilers, linkers, package managers, and the build pipelines that CI systems orchestrate.

Monorepo vs polyrepo, workspaces, package managers across ecosystems, lockfiles, semver, and the everyday governance of what depends on what.

Build the habits that let you verify changes, catch regressions early, and diagnose failures with confidence.

The three paradigm families every engineer should recognise — object-oriented, functional, and concurrent — both as cognitive tools and as guidance for which language fits which problem.

Understand how long-running services start, stop, fail, and recover on Linux — from processes and signals to systemd and service-level debugging.

Learn the everyday habits that reduce risk — safe secrets handling, SSH discipline, least privilege, and trustworthy tool usage.

Learn how to write the docs, runbooks, and change notes that make engineering work understandable, reviewable, and resilient.