![]() I came up with a review-based workflow with our Junior engineers: issues are discussed together via zoom (it also allows to annotate shared screen or record the session) and then I let the juniors work until the PR is ready. If you want to support my efforts, you can offer me a coffee ☕ or follow me on Twitter □ ! You can also support me directly via Paypal! I hope you enjoyed reading this article as much as I enjoyed writing it! If so, leave a ❤️ or a □ ! I write tech articles in my free time and like to drink coffee every once in a while. So, what are your experiences? What tools do you use? What are your best practices when it comes to remote pair programming? For me, coding together on the same machine still feels a lot more productive. I've played around with IntelliJ's pair programming feature for a bit, but not everyone uses IntelliJ either. Screen sharing works, don't get me wrong, but it's easier to point on something on screen with your finger than to figure out the lines (and read them aloud at the same time!) of some blurry editor while the other person is scrolling along. However, the remote situation has made pair programming rather rare, at least in my team. I've done this with peers for weeks on end. They come up with a plan together, write down open questions and then get going. Both people get to discuss their ideas and find the best solution together.įrom my experience, two people are usually working on the same computer. While the driver is doing the actual coding, the navigator tries to keep the overview and give directions to the driver. A popular approach to pair programming involves two roles: A driver and a navigator. ![]() It helps to onboard new team members to an existing application, give juniors an opportunity to learn from more senior devs (and vice versa!), discussing ideas and concepts. Pair programming is a very helpful technique. A specific topic I'd like to look at today is pair programming. And in this post I want to discuss some of these hurdles, and more specifically, how to overcome them. With the new remote situation came a few hurdles, though. (As a little disclaimer: I'll use the word "remote" in this post to describe non-onsite things in general, even if you're in the same town as your peers.) Video calls became a widespread norm, employees of some companies, like Twitter, can now work from home forever if they want. This hasn't stopped us from delivering amazing software and do good deeds though - Au contraire! Think of global remote hackathons, local efforts to create services that help people in need, providing schools with old laptops, the list goes on.Īrguably, the tech industry has adapted rather quickly. The certain situation the world has been in for the past almost two years has affected a lot of us devs all around the globe.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |