Timeline for Should I accept a job if pair programming is required?
Current License: CC BY-SA 2.5
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 17, 2021 at 9:18 | comment | added | Code Name Jack | Guess What, We always have been doing pair programming in some ways | |
| Dec 10, 2017 at 9:01 | comment | added | Giorgio | "Guess what - nobody likes pair programming at first.": Guess what - I did not like it after doing it for two years on a row. I left that company and in my new company / team nobody wants to do pair programming and we are all very happy and much more productive. In my experience, pair programming is only good for training beginners, for micromanaging, or for people who are not able to work on their own. | |
| Jul 13, 2016 at 12:35 | comment | added | Dib | I for one now ONLY want to program in a pair as the knowledge transfer is amazing, both for coding skills and IDE shortcuts. And for those germophobes - plug in your own keyboard and mouse and stick to your own when you are the driver! | |
| Jul 13, 2016 at 12:35 | comment | added | Dib | I found pair programming on this project helped me not go down blind alleys and rabbit holes that I have been prone to on single developer projects. When the project was released the project had lest bugs in test and the warranty period than any other of it's size in the company. We also have two developers who know the product intimately so the "hit by a bus" problem is less critical. | |
| Jul 13, 2016 at 12:35 | comment | added | Dib | I recently completed my first project using pair programming with a more senior developer in the team. We shared the piloting and co-piloting of complex tasks fairly evenly and we both learned a few things from each other. We did split for trivial, mundane or "boiler-plate" tasks. | |
| Dec 18, 2014 at 11:34 | comment | added | Giorgio | "After a week of this we deployed it.. and everything just worked. Not a single bug. Not one.": I haven't experienced a significant difference in number of bugs between using pair-programming and not using it. Discussing the essential points with your colleagues and then coding on your own can be as effective. Pair-programming is no silver bullet. | |
| Nov 15, 2011 at 10:32 | comment | added | Wizard79 | They basically told me your same exact story. People there were very supportive and I acknowledge that coding that way rocks - and improves your skills. But that was driving me crazy. I couldn't live with all the limitations to my "personal freedom" and "living space" (choosing the timing, listening to music, keyboard configuration, color scheme in the IDE etc.), so after few weeks I give up. | |
| Sep 29, 2010 at 1:29 | comment | added | dash-tom-bang | I would suggest that the OP will only succeed at a company like this if he's open to learning that he's not actually as good at programming as he thinks he is, and then comes around to wanting to learn how to get better. | |
| Sep 28, 2010 at 18:54 | history | answered | Jaco Pretorius | CC BY-SA 2.5 |