Did you just call all developers that don't like TDD and pairing as prima donas?
Do you release that's probably 90% of engineers out there, and maybe 95% of the good ones.
You can work and make great software without using heavy handed processes like TDD and Pairing, which in my opinion it only helps junior/inexperienced developers a bit, but hampers the productivity of the good ones.
But yea, it seems that the place wouldn't be a fit for him, but there is no need to call him a prima dona. He was right to stick with his guns, and you guys stick with yours, but keep in mind that you are limiting yourself to a very small subset of engineers that both like TDD/Pairing and are good at what they do.
Not at all. He just wasn't a good fit for the team, and nor was the team a good fit for him.
Prima-donna programmers tend to be vain, demanding, and incapable of receiving or acting on constructive criticism.
More often than not, they're also not particularly productive, either.
Whether or not you do TDD is unrelated to any of those personality traits, and I've interacted both with excellent developers that had a myriad of reasons to not test, as well as horrible prima-donnas that were religious about TDD, but only if you did it the One True Way That Only They Could Understand.
Do you release that's probably 90% of engineers out there, and maybe 95% of the good ones.
You can work and make great software without using heavy handed processes like TDD and Pairing, which in my opinion it only helps junior/inexperienced developers a bit, but hampers the productivity of the good ones.
But yea, it seems that the place wouldn't be a fit for him, but there is no need to call him a prima dona. He was right to stick with his guns, and you guys stick with yours, but keep in mind that you are limiting yourself to a very small subset of engineers that both like TDD/Pairing and are good at what they do.