Skip to content

Vol 0: Developer Workshop ​

This volume connects the terminal, Git, debugging, builds, containers, and deployment into one reproducible development loop. A failure should leave evidence, and a success should be repeatable; “works on my machine” is not a diagnostic format.

Prerequisites ​

  • Start here; no programming experience is required. You need a computer on which you can install development tools and basic familiarity with creating and editing text files.
  • Be ready to run small examples and explain the observed output, not just recognize terms.

Coverage ​

Start with how programs run, then practice the terminal and Git. The later chapters use debugging, builds, and containers to take a local change through a verifiable release. Each lab names its environment and cleanup steps.

Chapter 1 ​

Chapter 2 ​

Chapter 3 ​

Chapter 4 ​

Chapter 5 ​

Chapter 6 ​

Chapter 7 ​

Chapter 8 ​

Outcomes ​

  • Distinguish files, processes, threads, and memory, and inspect where a command comes from.
  • Record changes with Git and diagnose failures using stack traces, logs, and minimal reproductions.
  • Build an identifiable artifact and rehearse container startup, health checks, and rollback locally.

How to use this map ​

Read in order when the topic is new. For review, start from a chapter heading, open the smallest relevant lesson, and verify its completion check before moving on.

Built with VitePress | Software Systems Atlas