Live data from Hacker News

Things to Say When You're Losing a Technical Argument (2001)

pigdog.org

11–20 of 23 posts

Re: Things to Say When You're Losing a Technical Argument (2001)

#11
post #2

"Oh, my mistake. You're right. Thanks for pointing that out!" That is, if you're humble enough to put your ego aside.

Yes. I would go out of my way to not work with the author of this horror.

Given your response, I'd go out of my way not to work with you.

Seriously.

Re: Things to Say When You're Losing a Technical Argument (2001)

#13
post #2

"Oh, my mistake. You're right. Thanks for pointing that out!" That is, if you're humble enough to put your ego aside.

This is generally a good strategy even if it wasn't your mistake. Last week I wrote a short apology for something I'm sure I didn't do, which got my client in trouble with his business partner.

The business partner sent my client an angry email demanding to know how the mistake could have been made. It's very likely that it was the business partner's mistake, very unlikely that it was my clients mistake... but "oh, hey! our consultant was working near that issue, maybe he touched it?! We'll ask him right away, Mr. Angry Important Business Partner!"

Problem is: there's no possible way to know who did it. Shifting it back to the likely source (business partner's team) will only make him more angry, whether or not they are responsible. As a consultant, I can only loose.

So I write an email to him, CC my client, and apologize for the mistake, promising that it won't happen again. My client knows I didn't do it, and now knows that I willingly took the bullet for him.

Maybe SGaaS is a valid business model, where SG = scapegoat.

Re: Things to Say When You're Losing a Technical Argument (2001)

#14
post #2

"Oh, my mistake. You're right. Thanks for pointing that out!" That is, if you're humble enough to put your ego aside.

Sometimes conceding defeat so easily is the most frustrating thing for your opponent. It makes them feel like they only won because you didn't try.

I had a girlfriend complain "you always have to be right!" to which I replied "no, I'm just willing to admit when I am wrong". She objected, saying that I win every arguement. I recalled many occurances where she won arguements and pointed out how breif those discussions were because I allowed her to be right. Then she got even more angry at me for being right again...

Re: Things to Say When You're Losing a Technical Argument (2001)

#15
post #13
post #2

"Oh, my mistake. You're right. Thanks for pointing that out!" That is, if you're humble enough to put your ego aside.

This is generally a good strategy even if it wasn't your mistake. Last week I wrote a short apology for something I'm sure I didn't do, which got my client in trouble with his business partner. The business partner sent my client an angry email demanding to know how the mistake could have been made. It's very likely that it was the business partner's mistake, very unlikely that it was my clients mistake... but "oh, h…

Saying sorry (even for something you didn't do) is always a good strategy.

Another one of my favourites: Phrasing a request like you're asking a favour even though you're just telling someone to do their job.

Re: Things to Say When You're Losing a Technical Argument (2001)

#16
post #13
post #2

"Oh, my mistake. You're right. Thanks for pointing that out!" That is, if you're humble enough to put your ego aside.

This is generally a good strategy even if it wasn't your mistake. Last week I wrote a short apology for something I'm sure I didn't do, which got my client in trouble with his business partner. The business partner sent my client an angry email demanding to know how the mistake could have been made. It's very likely that it was the business partner's mistake, very unlikely that it was my clients mistake... but "oh, h…

Maybe SGaaS is a valid business model, where SG = scapegoat

One could argue that consultancy firms are already in this business, as you've just described.

When unpleasant decisions need to be made, hire a bunch of consultants who can 'rubber stamp' it so the management and board can pass the blame.

Re: Things to Say When You're Losing a Technical Argument (2001)

#17

There's also the generic "that's provably false".

"If that's true, it follows that P=NP"

"That would reduce to the halting problem"

Or my favorite,

"If you can solve that problem, there are much more lucrative applications for the technology than [what you're working on]"

Re: Things to Say When You're Losing a Technical Argument (2001)

#18
post #13
post #2

"Oh, my mistake. You're right. Thanks for pointing that out!" That is, if you're humble enough to put your ego aside.

This is generally a good strategy even if it wasn't your mistake. Last week I wrote a short apology for something I'm sure I didn't do, which got my client in trouble with his business partner. The business partner sent my client an angry email demanding to know how the mistake could have been made. It's very likely that it was the business partner's mistake, very unlikely that it was my clients mistake... but "oh, h…

A very good policy and good advice. Still, one should be careful about apologizing in a way that could bring them financial liability for something they actually were not responsible for.

Re: Things to Say When You're Losing a Technical Argument (2001)

#20

Earlier quoted context omitted.

Sometimes conceding defeat so easily is the most frustrating thing for your opponent. It makes them feel like they only won because you didn't try.

I had a girlfriend complain "you always have to be right!" to which I replied "no, I'm just willing to admit when I am wrong". She objected, saying that I win every arguement. I recalled many occurances where she won arguements and pointed out how breif those discussions were because I allowed her to be right. Then she got even more angry at me for being right again...

Notice he said 'I had a girlfriend', sometimes the best approach is knowing when being right is wrong.
Post reply on HN