...
Please try solving the issue on your own first (we are happy to provide you with a rubber duck), before consulting someone else but don’t be afraid to interrupt another engineer if you need help. Find someone and explain what you’re trying to solve and how you think you want to approach it and you might even get a second opinion or a pair programming session out of it.
Pair-programming
...
🤝
Writing Code in pairs or even doing the occasional mob programming session is not a mandatory part of our workflow, but highly encouraged. Especially during your onboarding phase or when you take over a new project, your peers will be happy to pair with you. But also after the first few months, if you enjoy this style of working and all the advantages that come with it, from sharing knowledge to getting your code review “on the go“, check with your peers during planning and grooming sessions which stories you want to pair on.
Some Best Practices for your Pair Programming Sessions:
Check Tools Like CodeTogether to collaborate remotely directly within your IDE
Switch Driver and Navigator Roles often to keep focus and engagement
When you are the driver, talk through what you’re doing as you are doing it
When you are the navigator, give directions on the bigger picture and share your thoughts but avoid micromanaging the driver
Keep your pair programming sessions to a few hours max, pairing for the entire day can get quite exhausting and doesn’t yield the best results