[hrktb]

It’s seldom straight lying and more often omission of critical facts or misrepresentation of their roles on projects. Which sadly is the common advice given to people writing resumes, and it becomes a prisonner’s dilemma.

I assisted at whole interviews where “tech leads’ craftily avoid recognizing they code at most half an hour a day.

Or a dev listing super hard stuff on their resume but never mentioning until thoroughly asked that they pair programmed all of these.

[411111111111111]

Why is pair programming an issue here?

Personally I find pair programming hard stuff way better, because your constantly talking about the challenge a find issues earlier than when you just implement your initial solution.

I never thought that is somehow bad, but I guess people have different worldviews

[hrktb]

It is not bad by any mean. It is essential information that should not be set aside though.

It’s like co-authoring a book, that’s fine, but don’t just say “I wrote a book about xxxx”, be upfront about cowriting it.