Time for the #DevDiscuss Twitter chat! Tonight's topic is PAIR PROGRAMMING
Here are some jump-off questions:
Do you pair program?
If so, how often?
What are the benefits of pair programming?
The chat will last about an hour and we use the #DevDiscuss tag.
Rules:
- Stay on topic
- ALWAYS ALWAYS use hashtag #DevDiscuss
- Be NICE/POSITIVE ❤️
- Quoting tweets for clarity is encouraged
(ALWAYS use the #DevDiscuss, even on replies where appropriate 😄)
Time for the #DevDiscuss Twitter chat! Tonight's topic is PAIR PROGRAMMING
Here are some jump-off questions:
Do you pair program?
If so, how often?
What are the benefits of pair programming?
I haven't had the opportunity to pair program but I enjoy the pair programming videos I've seen on @pluralsight and see value in the concept. #devdiscuss
I've pair programmed a few times at work, I found it really helpful to pick up new programming techniques and patterns since I get to talk through it and get hands on with the code #devdiscuss
Yes! I've been pair programming for the past few months and it's been a great way to get feedback on code / style, as well as speed up the onboarding process and familiarity with data / infrastructure.
#DevDiscuss
Pair programming means something different to every company & team.
To some its..
"lets tackle this problem together"
"you type, I'll talk you through it"
"you type, I'll stare awkwardly"
"lets work on the same branch on our own computers"
etc
#DevDiscuss
I haven't done pair programming before, but I'd love to try it. So far I've contributed to a couple of open source projects, but I'd like to work with another dev sometime on building a project together #DevDiscuss
I am curious to hear what people think about livecoding (livestreaming programming). It's like pair programming, but with an entire crowd watching and interacting in chat. #devdiscuss
I like pair programming when there's a new feature that needs some architectural updates.. or when there's some a lot of refactoring that needs to be done.
Benefits are less refactoring later and having a cleaner solution right away. #DevDiscuss
My team pairs infrequently.
If it's complicated enough to benefit from two engineers looking at it simultaneously, it was probably already hashed out in a design doc. #DevDiscuss
Also it helps when you get to pair program with "senior" devs and you two get stuck and kind of bounce ideas off each other. Makes it another way to get close with your fellow teammates #devdiscuss
Time for the #DevDiscuss Twitter chat! Tonight's topic is PAIR PROGRAMMING
Here are some jump-off questions:
Do you pair program?
If so, how often?
What are the benefits of pair programming?
Pair programming's an excellent way to ease somebody into the team, teaching them about the codebase and the intricacies of the product, just overall making them more comfortable and trusting.
I don't like doing it for too long, though, as it may "clip their wings".
#DevDiscuss
I learn a lot by watching other people code. Even if I'm familiar with the project or language, I've picked up lots of great workflow tips, keyboard shortcuts, and other interesting tidbits by seeing the way that others approach a given problem. #DevDiscuss
Other benefits are.... TEAM COMMUNICATION!
Sometimes code is a good way to open the lines of communication and you'll feel more comfortable asking for help later. :)
#DevDiscuss
I'm a solo shop. There's no pair. I wonder if that would be an opportunity for a really cool social network of solo devs. You look at mine and I'll look at yours... #devdiscuss
I enjoy pairing every so often, but I have a hard time with it for extended periods of time. Just not how my brain is paced. Some folks are pretty religiously for or against pairing, but that absolute mindset wouldn't work for me. #DevDiscuss
Time for the #DevDiscuss Twitter chat! Tonight's topic is PAIR PROGRAMMING
Here are some jump-off questions:
Do you pair program?
If so, how often?
What are the benefits of pair programming?
A common mistake managers make is to say “if we weren’t pair programming, we could deliver faster.” This presupposes that everyone already understands the problems at hand equally well, and that there isn’t value in multiple developers understanding the same problem. #DevDiscuss
We've talked about pair programming at work, but I haven't done this in quite some time. Most of my experience is in working closely with a key stakeholder, rather than another developer. #DevDiscuss
I am curious to hear what people think about livecoding (livestreaming programming). It's like pair programming, but with an entire crowd watching and interacting in chat. #devdiscuss
Here’s my major gripe with pair programming. When I code I have to concentrate. I can’t concentrate with someone staring over my shoulder. Code reviews, debugging, that makes sense in a collaborative setting. Pair programming, to me, is just counter-intuitive. #DevDiscuss
When I started developing, I feared pair programming and I think it was because it was often done poorly (the pairing and the code)
Now I love to pair with any level of developer because it’s an opportunity to learn
#DevDiscuss
Time for the #DevDiscuss Twitter chat! Tonight's topic is PAIR PROGRAMMING
Here are some jump-off questions:
Do you pair program?
If so, how often?
What are the benefits of pair programming?
Never did it at work, but at the university.
You're getting feedback on your code and can better dive in into huge projects when you're always talking about the modules/components you're working on.
So you learn a lot with PP.
#DevDiscuss
We see this benefit from our engineers observing one another. Everybody learns something from theses. Not necessarily about how to engineer but workflows, best practices, ways to be more efficent.... #DevDiscuss
Yes! Pair programming is good for when you’re teaching newer developers, too - you can point out smaller syntax errors when they get stuck, & for other bugs, searching for answers online together helps them hone their searching skills to find the solution. #DevDiscuss
Pair programming is important since collaborating and working with others is part of a dev's regular day. It gives everyone a chance to help each other and combine individual strengths together to create unique solutions to user problems #devdiscuss
Pair programming's an excellent way to ease somebody into the team, teaching them about the codebase and the intricacies of the product, just overall making them more comfortable and trusting.
I don't like doing it for too long, though, as it may "clip their wings".
#DevDiscuss
I think it's good if you're stuck on a problem. Another set of eyes definitely helps. I don't think it needs to be a constant thing though. If a solution is clear in my head, I'd rather go on my own. Major negative... who gets to type? 😉#devdiscuss
The more I think about "pair programming", it seems that the emphasis is on the "pair". If one of you is sitting and watching, with no talking, then something seems wrong. There should be dialog, exchange, or demonstrations. #DevDiscuss
Another important point - mob and pair programming are NOT for everyone. I don't like when companies 'force' you into doing it. We all work best in our own ways && companies should encourage that.
However you should be open to collaboration when it benefits the team.
#DevDiscuss
I've taken part in mob programming at a meetup and it was pretty fun. Only one person is under the spotlight at a time and it was never me, so that makes things much less nerve-racking. #devdiscuss
My team at work pair programs and even mob programs frequently. It’s a great way to on-board, mentor, share knowledge, tackle a tough task or learn a new topic together. #DevDiscuss
I voted for pair programming as tonight’s topic to see if people still practiced it. Thought it may be a fade that passed. No one I’ve ever worked wanted to try it. #DevDiscuss
Time for the #DevDiscuss Twitter chat! Tonight's topic is PAIR PROGRAMMING
Here are some jump-off questions:
Do you pair program?
If so, how often?
What are the benefits of pair programming?
I feel like the time spent makes a difference. An hour a day is probably too much, but an hour a week is bite-sized, would help both participants learn, and can be seen as a team-building experience. #DevDiscuss
Time for the #DevDiscuss Twitter chat! Tonight's topic is PAIR PROGRAMMING
Here are some jump-off questions:
Do you pair program?
If so, how often?
What are the benefits of pair programming?
We also find TDD helpful when pairing or mobbing. It gives everyone a common thread to focus on, we high five when the test(s) turn green.
Breaks and days to solo program are certainly needed to help balance. It can be intense collaborating *all* the time.
#DevDiscuss
Time for the #DevDiscuss Twitter chat! Tonight's topic is PAIR PROGRAMMING
Here are some jump-off questions:
Do you pair program?
If so, how often?
What are the benefits of pair programming?
#devdiscuss I have been doing a lot of pair programming lately. It helps when 2 people put their heads together. They collectively come up with better ideas, better solutions, find stupid things before they happen, and walk away with a common base that serves as a launching pad
There are pros and cons, and of course - it depends on your definition.
Pros: New approaches to problem solving, stronger relationships, correction of bad practices.
Cons: Can be inefficient, particularly if it is done often - such as the way PluralSight does it. #DevDiscuss
I like the idea of talking through a problem with another dev. Or having another dev review your code, but typing while someone else is talking, etc is my nightmare #DevDiscuss
Mob Programming has been great, check out @WoodyZuill’s work!
We have laptop plugged into a TV. We set a timer on an iPad for 10 minutes and pass a Bluetooth keyboard and mouse around at each interval.
#DevDiscuss
In reply to
@ajw1970, @ThePracticalDev, @WoodyZuill
I was originally very skeptical of pair programming, but found that the ability to learn/teach and especially identify bugs quickly made it a very valuable technique. I think it especially serves new employees well to learn about existing code base. #DevDiscuss
At least 1-3 hours a day, with dozens of different people. It:
- Forces you to explain (and better understand) problems
- Keep devs unblocked
- Grows skills
- Builds confidence in teammates
- Brings consistency to a codebase
- is fun
#DevDiscuss
#DevDiscuss I have been doing a lot of pair programming lately. It helps when 2 people put their heads together. They collectively come up with better ideas, better solutions, find stupid things before they happen, and walk away with a common base that serves as a launching pad
Time for the #DevDiscuss Twitter chat! Tonight's topic is PAIR PROGRAMMING
Here are some jump-off questions:
Do you pair program?
If so, how often?
What are the benefits of pair programming?
I like to set up frequent meetings throughout the day and catch up/go over work. It keeps me and other devs in sync but let's us take time to think through on our own #DevDiscuss
Depends on the ticket but we mostly do it daily. As a junior it is invaluable to see the thought process and best practices of seniors and removes the "freakout" phase of daunting tickets when you can work through it with someone sometimes #devdiscuss
Pair programming has really helped me get over some of the initial hurdles I’ve faced trying to learn programming. I only wish I had accepted this kind of help sooner. Thanks @DaveChappell!
tl;dr Don’t be afraid of pair programming!
#DevDiscuss
Time for the #DevDiscuss Twitter chat! Tonight's topic is PAIR PROGRAMMING
Here are some jump-off questions:
Do you pair program?
If so, how often?
What are the benefits of pair programming?
We don't have company requirements for IDE/Editor, but pair programming has let me see other peoples' IDEs and workflows, which has led to some workflow changes and efficiency improvements for both parties. #DevDiscuss
At work we often do Pragmatic Pairing. If the sotry/taskbar hand is soo small doesn't require pairing.
Benefits:
4 eyes are better than 2.
You have to reason out each design/code and hence more clean.
Knowledge/context sharing .
@ThePracticalDev#DevDiscuss
Pair programming is essential for junior devs. Pairing juniors with senior devs promotes an accelerated learning path. On the other side for senior devs, it is extremely beneficial by deepening their knowledge through teaching and growing as leaders. #devdiscuss
I've had great experiences with mob programming when exploring a new tech or a difficult problem. It's the same as pair programming, but with more people around. Keeps a larger team in the loop, and ensures everyone learns from that coding session. #DevDiscuss
Asking for help is the hardest thing for me. I ALWAYS assume I should know something I dont, even after years of telling others how wring that notion is. Pair programming works #DevDiscuss
Pair programming has really helped me get over some of the initial hurdles I’ve faced trying to learn programming. I only wish I had accepted this kind of help sooner. Thanks @DaveChappell!
tl;dr Don’t be afraid of pair programming!
#DevDiscuss
Time for the #DevDiscuss Twitter chat! Tonight's topic is PAIR PROGRAMMING
Here are some jump-off questions:
Do you pair program?
If so, how often?
What are the benefits of pair programming?
At work we often do Pragmatic Pairing. If the story/task at hand is soo small doesn't require pairing.
Benefits:
4 eyes are better than 2.
You have to reason out design/code and hence more clean.
Knowledge/context sharing .
@ThePracticalDev#DevDiscuss
I had dabbled in pair programming before, but never really valued it. It's been amazing on my latest project, though! Mostly we work independently, but if any of us get stuck we hop on a call, screen share, & brainstorm together. Nobody spins their wheels for long! #DevDiscuss
Pair programming can be scary when you first get started (especially if you're new to the company / problem / language), but once you get going, it's great to:
+ learn new ways of doing things
+ build trust and bond with your team
+ improve workflow / efficiency
#devdiscuss
For companies exploring pair-programming, are you really seeing sufficient ROI to justify two full-time devs for each dev task? Where are you seeing that ROI? (reduced task-completion time, bug reduction, …)
#devdiscuss
I've been pair programming every day for almost two years and I think it's a great tool to share knowledge, guarantee code quality and also to get to know people on your team better #DevDiscuss
It can be awkward at the beginning when you are who is typing , but it also can be a good challenge and a nice way to teach and learn different things not only technical and you can be more close and sync with your team #DevDiscuss
An easy way is to pass it to the player on the left after X time or after an item has been worked on. In practice, it often ends up depending on the energy of each team member, and how comfortable they are by being on the spotlight. #DevDiscuss
Been doing pair programming for a while now and it still my favorite teaching/learning method. For me it is also a way to keep focused on what I'm doing, since is harder to multitask when you have someone else with you on that period.
#DevDiscuss
Time for the #DevDiscuss Twitter chat! Tonight's topic is PAIR PROGRAMMING
Here are some jump-off questions:
Do you pair program?
If so, how often?
What are the benefits of pair programming?
I would think it would be helpful to maintain balanced skillsets. Those who are always learning can also gain from sharing what they learn. #DevDiscuss
Ach, I'm late to the #DevDiscuss party, but my two cents: it's useful when you need it to be. I work in C#, but I'm terrible at LINQ. On our latest project, my senior and I have started pair programming via screen share. We've both benefitted more from it.
In college on a senior project me and a friend decided to do pair programming on our own. Hooked up 2 keyboards and mice to the same computer. Worked great, however I have found someone else since then that we are close enough to be able to pull that off. #DevDiscuss
In college on a senior project me and a friend decided to do pair programming on our own. Hooked up 2 keyboards and mice to the same computer. Worked great, however I haven’t found someone else since then that we are close enough to be able to pull that off. #DevDiscuss
An often overlooked benefit of pair programming is the lack of external distractions. If you are working with another dev next to you, it's much more unlikely that someone may interrupt, or that you'll alt tab to check Slack while waiting for a test to run. #DevDiscuss
I'd be curious to see empirical data; but my limited experience suggests that while pair-programming, the devs involved tend to stay more focused on the task at hand, with less likelihood to go off on tangents or getting distracted by something else. #devdiscuss
I think pairing is great, Just that no one else seems to want to. But this reminds part of the issue might be me, easier just to work at your desk then get up and ask someone if they want to pair. #DevDiscuss
I was able to help turn around an angry customer on the road this month during a problematic mechanical installation of a coil processing line. I do the machine control programming on that line but am also quite familiar with the machinery. #DevDiscuss
I really enjoy pair programming. It's typically a daily occurrence for me and ranges in amount of time. IMO, it can build stronger relationships among teams. I often feel the work gets done in a fraction of the time with better quality as well. #DevDiscuss
I've seen it work and not. My friend @bruncun actually live-streamed his first Stimulus app and made a talk from his experience. There are also some interesting tools to help make sense of it all like @glitch (for Node).
#devdiscuss
