Thread by @tottinge

@eikonne I also find the pair-programming he’s referring to to be suboptimal.
For me to type all day while you criticize, or for me to criticize all day while you type (worker/watcher or worker/critique) is indeed a very dull and wasteful thing.

Pair Programming, on the other hand…

@eikonne … actual pair programming by co-creating code, switching roles frequently, switching partners a few times a day, is not only an excellent pedagogical tool but a great way to do work.
It also means you don’t break tasks down to individual skills, but work more whole features.

@eikonne I think that this is a classic (AKA "normal") case of confusing the antipatterns for the thing.

"Doing dishes sucks: all that food floating in dishwater"
"Dude, that's wrong. You're supposed to scrape and rinse them first."
"Oh, you purists and your No True Scotsman fallacy!"

@eikonne "Seriously, that's not how you do dishes."
"Why do you think you're better than me, you elitist!"
"No, you're just washing dishes wrong."
"Face it: washing dishes is just disgusting and that's all."

@eikonne Everything has these misuse patterns, and the thing that qualifies them as misuse patterns is that they take the benefits and joy out of the real thing.

Same for agile, pairing, ensemble, tdd, automated testing, manual testing, management, all.

@eikonne Maybe we're doing a poor job of communicating what a thing really is, or maybe people just take the sound bite and run with it. I dunno. But what a lot of people doing rightly does such, b/c they're trying to make the misuse pattern work instead of the real thing.

@eikonne It's not like the antipatterns are kept secret, or the proper way is kept secret unless you count it being "locked away" in countless books and blog posts and videos on the internet as "hidden."
One has only to look.
Or ask.