3 ms·
IMO, there is no magical formula, and being a senior dev doesn't change the work involved: you're still developing code, you're still working with your peers, y
by falcolas 9y ago
IMO, there is no magical formula, and being a senior dev doesn't change the work involved: you're still developing code, you're still working with your peers, you're still designing stuff. You're just better at it because you've seen a lot of it before.
That means you'll get productive in same way you'd become productive as a junior. Pick up easy tickets and use them to learn to navigate the codebase. Talk to your colleagues and fill in your knowledge gaps. Help others who are having issues. Pick up and address more tickets. Get in the thick of things as quickly as possible.
If the position includes additional roles, such as that of a PM, nail down the necessary role requirements and start doing those as well. You'll need to work on your soft skills - honey and vinegar, carrot and stick, etc.
You're a senior developer because of your experience and knowledge in general, not because you're magically a productivity machine. Assumptions are going to be your biggest hinderance when coming in to your first "senior" position. Don't assume that you know more than your peers, even the junior ones; when you first start they probably know more about the codebase and tech stack than you do. Don't assume that if a team works differently than what you're used to, it's automatically worse. Don't assume that their code quality and engineering practices are poor.
Don't assume; find the reality and work with your team from there.