Analysis

404: Uncle Marcus

Your uncle is missing. His last release is broken. The clues are in the code — if you know how to read them.

Intermediate
45
mins Certificate included
See Plans Back to Courses
404: Uncle Marcus

Course overview

About this course

Your uncle Marcus is missing. The release he deployed on Friday night is broken in a way nobody can explain. On his desk: a laptop, still open. A sticky note reads: "If you're reading this, you know what to do. Start with the logs." Decode the deployment logs, trace the broken sequence diagram, find the missing requirement — and crack the safe that will tell you who took him and why.

What you'll learn

Practical outcomes

  • How to read a deployment log and identify meaningful error patterns.
  • How to read and interpret a sequence diagram to spot missing steps.
  • How requirements gaps and deliberately removed acceptance criteria cause production failures.
  • How to identify NFR failures in API response data.
  • How to write a blameless post-mortem that identifies systemic causes rather than individuals.

Pre-requisites

What you should know first

  • Recommended: The Broken Backlog, or existing knowledge of user stories and acceptance criteria.
  • No technical background required — all concepts are taught within the course.

Ready to begin?

Start learning through real challenges

Work through interactive exercises, unlock the next steps as you progress, and earn a certificate on completion.

See Plans
Subscribe to Analysis