Dev Voyage: Calm Sea
- 1Part 1·4 min read·BeginnerUp next
Your First 90 Days: How to Join a Crew Without Sinking
Trying to look fast in your first months hides how lost you are and leaves you judged against expectations nobody wrote down. Write a 30-60-90 plan in week one, agree it with your lead, and check it every two weeks.
- 2Part 2·4 min read·Beginner
Ask Better Questions: The Skill That Saves Your First Month
Staying stuck in silence costs days on a problem a colleague answers in two minutes. Try for a time box, then ask once, in public, with what you tried, what you saw and what you need, and write the answer down.
- 3Part 3·4 min read·Beginner
Make Friends on the Ship: Working Happily With Colleagues
Misreading a short reply or correcting a senior in public keeps you a guest on the team. Build trust in small, repeated acts: public thanks by name, ten-minute help, and corrections made privately first.
- 4Part 4·4 min read·Intermediate
When You Break Something: Owning a Mistake Without Losing Trust
Fixing a production break quietly leaves customers failing while you hide it. Say it within minutes, roll back before you debug, then write an incident note that blames the gap in the system, not a person.
- 5Part 5·4 min read·Beginner
Pass Probation on Purpose
Waiting for the probation verdict means learning at week 12 what was expected at week 2. Ask what passing means and write it down, keep a brag doc every Friday, and ask what worries your lead at the midpoint.