>Honest question here, is pair programming still a thing?
It's still by far the most effective tool for certain tasks. Inherit an extremely complex codebase with 50 levels of abstraction? You could spend a week tinkering with it, or you could step through the code with the guy who wrote it for 30 minutes. But it's not something you'd want to do every day, or even frequently.
It's still by far the most effective tool for certain tasks. Inherit an extremely complex codebase with 50 levels of abstraction? You could spend a week tinkering with it, or you could step through the code with the guy who wrote it for 30 minutes. But it's not something you'd want to do every day, or even frequently.