Stage 1 · Lesson 6 of 7
Light preparation, not cramming
Teams expect to teach a new joiner their system, so you do not need to master everything before you start. A little is all you need. Refresh the basics of the language and named in the job description.
Make sure you are comfortable with , the and your editor. If you like, read the first chapters of a book about working as an engineer. That is enough.
Rest, sort out travel or your home desk, and sleep well; these matter more than a tenth tutorial. Good basics help you pick up the team's own knowledge quickly in the first two weeks, which is where the real learning happens.
Common trapspending your cramming frameworks the team may not even use, and arriving already tired.
A question to check yourself, an AI practice session and 1 cheat sheet entry come when you add the roadmap to your account. Add it
Resources for this stage
Start with· follow one of these
- GuideFreeJob Scams (FTC Consumer Advice)
US Federal Trade Commission
The warning signs of fake job offers and payment requests, useful wherever you live
- BookPaidThe Missing README: A Guide for the New Software Engineer
Chris Riccomini and Dmitriy Ryaboy (No Starch Press) · Beginner · $29.99 print, $23.99 ebook
Read the first two chapters before you start: what the first year looks like and how you will learn
Practise
Keep handy
Also worth your time
- The Pragmatic EngineerGo deeper
How tech companies work from the inside, when you want the wider picture of your new industry