After you've signed the contract for a new role, there is likely to be some confusingly organised onboarding. You'll navigate how the team speaks to each other and how they discuss their priorities and values. You are likely to get questions passed around, and some vague 'documentation' on a complex system. No one gets a chance to review it more than once a year so... That means processes have changed. The coding standards are different now. These are the general frustrations of the average company, where people focus on velocity more than the comfort of incoming colleagues. Many new hires will take the time not to rock the boat . To put their head down and build some velocity. And that's a great strategy, if you want to become someone known for pushing good feature code and a 'safe pair of hands.' The 'safe pair of hands' is someone we can trust to get things done, they are reliable, docile, and mostly invisible.…