(highlight:: First and foremost, meet the team! Book in 121's, intros, catch ups with the team, major stakeholders, data 'gatekeepers' etc etc. Make sure you've got regular catch ups booked in with your line manager, set expectations/development goals/progress tracking. I'm assuming you've gained a promotion, but don't let that stop you from thinking about what you need to not only develop in role but what you need to be developing to become the best in role ready for a next step in a year or two.
Find out what you're gonna be working on and start learning about it. Does the database you're extracting data from have hidden quirks or rules you'd only learn about from experienced colleagues? Is there a data dictionary anywhere that's up to date and used/useful?
Access. Do you have the correct permissions/roles/technology to hit the ground running or is there going to be a period where you're waiting for a laptop and things to be installed approved?
Are there any good github repositories, examples of current or previous work, anything like that you can look over?
My personal favourite here as well. QA. Who enjoys QA? Absolutely fucking no one, but it needs doing and it's a great way to learn how the team codes and where stuff comes from whilst actually running things in their environment, plus, if you put your hand up for QA everyone is gonna love you, and it's a great way to get people to talk through their code and work whilst gaining an understanding of how the team functions.
Those are just a few off the top of my head, and I'm sure there's probably better and more important things to think about, but they always get me started.
Good luck!)
- No location available
-