I'm on the coding is intuitive side as well, though I see pairing more as a practice where you meld aesthetics rather than one person deciding everything. Sometimes long arguments break out, but you both should become better at the end of it.
Reminds me of a joke I've heard: "When you pair with someone you're pairing with everyone else they've ever paired with"
If this is true, maybe pair programming is just getting the underlying disagreements out in the open sooner, before they fester into something that will break the project.
continuing @ykgoon's marriage analogy, sometimes it's healthier for the marriage to have the argument than to avoid it and quietly resent each other.
@nindokag @riga @ykgoon @jamescgibson definitely a shared aesthetic, but it won't ever be 100% since everybody comes with a different background, and where it isn't 100% is where the most interesting conversations and arguments come from.
A lot of people I've worked with all have a pairing ancestor in common, where we've either learned pairing from them or are at least 1 degree away. We still probably have two or three big arguments/discussions a week.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!