onboarding
- Building relationships
- https://medium.com/@mrabkin/the-art-of-the-awkward-1-1-f4e1dcbd1c5c?hidden=true
- https://boz.com/articles/career-cold-start?hidden=true
- Onboarding mentality
- 2. learn the workflow of the new team, get into code but start with small changes
- 3. known issues may have be chosen not to be fixed by the team - work out why! understand tactical decisions
- 4. understand strategic decisions, align your decision making process with the team
- Asking for help
- as you grow as an engineer, you want to grow P&D and reduce T
- conversely, by narrowing the scope, you can become the expert in an area
- treat your set up as urgent → get help and become independent as soon as you can
- building your relationship with your buddy, example agenda
- what are you working on?
- what's top of mind for you?
- Learning the codebase
- what's been surprising? do you have any feedback for me?
- Make work visible - it helps people if you ask in a public forum and people can see
- What matters is **DOING**. You need to dig in and start coding
- To pick up a code base quickly, you need to work out what matters and what doesn't
- Don't try to tackle massive complexity head-on. Find quick wins and get runs on the board
- There's intrinsic complexity and accidental complexity. You want to run away from accidental complexity where you can
- There's so much you could learn but you need to prioritise and make the most of your time
- you should focus on the most important components
- Come back to these once you're more established
onboarding
- Building relationships
- https://medium.com/@mrabkin/the-art-of-the-awkward-1-1-f4e1dcbd1c5c?hidden=true
- https://boz.com/articles/career-cold-start?hidden=true
- Onboarding mentality
- 2. learn the workflow of the new team, get into code but start with small changes
- 3. known issues may have be chosen not to be fixed by the team - work out why! understand tactical decisions
- 4. understand strategic decisions, align your decision making process with the team
- Asking for help
- as you grow as an engineer, you want to grow P&D and reduce T
- conversely, by narrowing the scope, you can become the expert in an area
- treat your set up as urgent → get help and become independent as soon as you can
- building your relationship with your buddy, example agenda
- what are you working on?
- what's top of mind for you?
- Learning the codebase
- what's been surprising? do you have any feedback for me?
- Make work visible - it helps people if you ask in a public forum and people can see
- What matters is **DOING**. You need to dig in and start coding
- To pick up a code base quickly, you need to work out what matters and what doesn't
- Don't try to tackle massive complexity head-on. Find quick wins and get runs on the board
- There's intrinsic complexity and accidental complexity. You want to run away from accidental complexity where you can
- There's so much you could learn but you need to prioritise and make the most of your time
- you should focus on the most important components
- Come back to these once you're more established