Orientation: the chapter that decides whether the job sticks

1. The promise

You'll know what this chapter is for, what it does not contain, and why it is the last chapter of the course. You won't write any code in it. You'll read it the way you'd read a letter from a colleague who took the time to write to you before your first day.

2. The mental model

Every other chapter in this course was instruction. This chapter is the briefing your author would have given you over coffee in week one of your first job. It's shorter than it looks, because you're no longer being taught. You're being told.

You paid A$4,000. You sat through thirty chapters. You got the offer. Now somebody is about to give you a laptop, a badge, and a JIRA login, and nobody is going to tell you the things in this chapter. Most teams assume juniors already know them. They don't.

A term to define before we go further. Probation is the formal trial period at the start of a job, usually three or six months, during which either side can end the employment more easily. This chapter is about what to do during it.

3. What this chapter is, and is not

What this chapter is not:

• More code. No frameworks. No tooling. You've had enough of those.
• Career-coach material. No "find your why" exercises. No vision boards.
• Networking advice. No LinkedIn tips. No personal-brand talk.
• Generic. Every unit is about something that actually happens in a first engineering job.

What this chapter is:

• The things that decide whether your next three months end with a passed probation or a quiet conversation about fit.
• Sixteen short content units, in order, and one long assignment at the end.
• A send-off. After unit 31.15, the author has nothing more to say.

The shape on disk:

(SCREENSHOT: the chapter index for Ch 31 — full window — the orientation unit highlighted, padlock icons visible on units 31.1 onwards)

Unit 31.0 is free, the way the first unit of every chapter is free. Everything from 31.1 onwards is paid. The assignment at the end is paid and gated. That mirrors every other chapter you've read.

4. What you should be seeing

Three things in your head:

1. This is the last chapter. There is no Ch 32. After the assignment, you're on your own. That is the point.
2. The order matters. Don't skip ahead to 31.11 because salary is what you came for. The salary unit assumes you've already read 31.1 through 31.10.
3. 31.8 is the one most juniors need. It names the seven non-technical patterns that get juniors fired. None of them are about code. Read it carefully when you get there.

If you can name those three things without scrolling back up, you're done with this unit.

5. Common stumbles

• You treat this chapter as optional because you already got the job. The job is the start of the work, not the end of it. The chapter exists because the offer letter is the easy part.
• You skip ahead to 31.11 for the salary section. The numbers there don't help if you haven't read what behaviour earns the raise. Read in order.
• You read it once, store it away, and never look at it again. Re-read 31.8 in month three. Re-read 31.14 the first time you feel Sunday-night dread. The chapter is a reference, not a one-off.

6. You should know