A static archive of Markus Tacker's tweets. Follow me on Mastodon: @[email protected].
@Sarky_de This obviously depends on the
situation when you join the team, but it's always important to start with
listening to the team: do intensive 1:1 sessions with everyone in the first
week, and then continue to have 30min 1:1s every week with everybody in your
team.
@Sarky_de Clearly define, how you can be
reached, and provide clear guidelines for them to understand when you are
available for chat, and when you wish not to be disturbed. Check out this post
on the topic:
https://coderbyheart.com/define-a-communication-policy-so-slack-doesnt-kill-you/
@Sarky_de Resist the urge to change to much
right away, instead ask a lot of questions (no judging!) and use the first
months to get a detailed understanding of roles, competences and the whole tech
stack. Share your observations with the team, an outside perspective is super
valuable.