6 ms·
Pair Programming as a first-class citizen is stupid.
by goatcode 5y ago
Pair Programming as a first-class citizen is stupid.
- Jtsummers 5y agoWhat does this mean? As in, "Pair Programming as a mandatory thing is stupid"? That's sensible, otherwise this is hard to parse. It's a tool/technique, like rubber duck debugging with a person present to bounce ideas off of in real-time. It works for some people, it doesn't for others. Use it if it works for you, don't if it doesn't.
- jstx1 5y agoThat's reasonable. But there are companies out there that pair 100% of the time - no code is ever written by a single person. Sounds like hell.
- angrais 5y agoWhat would make it hell for you?
- Jtsummers 5y agoI think GP is referring to the 100% pair programming being hell. Pair programming all the time would be hell if you didn't get to choose your partner and/or you needed time away from them for any reason. Do you really want to spend every moment programming sitting next to some other person with one of you driving and the other speaking? Every moment? Maybe if you find the right partner (I had a couple colleagues who, for all practical purposes, were always paired with each other). But good luck finding that in every office you could ever work in.
- goatcode 5y ago> mandatory Pretty much that, or as the first place to go every time, for every card, by everyone. I agree with you: it's a useful tool, but it should be natural and any policy around it should be mutable.
- cloche 5y agoPair Programming is always suggested by the worst programmers.
- fshbbdssbbgdd 5y agoI sometimes suggest pair programming to help my colleagues when they are blocked. Does that make me a bad programmer?