What's the opposite of a sweet spot? Pain spot? Pair programming has a big one. Basically whenever you sit with another programmer and try to do initial design

What's the opposite of a sweet spot? Pain spot? Pair programming has a big one. Basically whenever you sit with another programmer and try to do initial design of something while coding it. God that is awful. Don't ever do that. But it is useful for other purposes. Two people think better than one, when the solution space is well defined. And you always pick up, or teach, some good tricks and habits from other people. If you're working on some code that you wrote yourself, you also learn a lot about how easy it is for others to understand it. The pitch for pair programming should not be increased productivity - at least not directly. Almost everything about the setup means things are slower. The benefits are in other areas, and are real. That said, the fact that you are two people means that you are 100% focused and not goofing off and procrastinating, so in the end you get things done just about as fast as you would have alone. It's pretty exhausting though, I would not recommend it for more than a few hours in one day, at most one or two times a week. Also, cool song :)