# Working as a Developer

> The human side of the job nobody puts in a syllabus - code review, reading someone else's mess, asking good questions, surviving your first on-call, and interviews that don't feel like hazing.

5 guides.

- [Code Review Etiquette](https://themissingmanual.dev/guides/code-review-etiquette) _(beginner)_ - How to give and receive code review feedback without damaging the relationship: tone, phrasing, picking your battles, handling criticism without getting defensive, and the unwritten norms nobody explains.
- [Reading Legacy Code](https://themissingmanual.dev/guides/reading-legacy-code) _(beginner)_ - How to make sense of an unfamiliar, undocumented codebase without reading it top to bottom - and how to tell when it actually needs a rewrite.
- [Asking Good Questions](https://themissingmanual.dev/guides/asking-good-questions) _(beginner)_ - How to ask questions at work that get fast, useful answers: being specific, showing your work, avoiding the XY problem, and picking the right channel for the moment.
- [Your First On-Call](https://themissingmanual.dev/guides/your-first-on-call) _(beginner)_ - What it's actually like to carry the pager for the first time: getting set up before your shift starts, staying calm through the 3am page, and turning the aftermath into a blameless postmortem instead of a blame session.
- [Technical Interviews Without the Hazing](https://themissingmanual.dev/guides/technical-interviews) _(beginner)_ - What technical interviews are actually evaluating, how to survive the coding round without panicking, and how to handle system design and behavioral rounds - including what to ask them and how to think about an offer.