public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin-talk@cygwin.com
Subject: Re: Constructive criticism
Date: Thu, 29 Jul 2010 14:52:00 -0000	[thread overview]
Message-ID: <20100729145211.GA20303@ednor.casa.cgf.cx> (raw)
In-Reply-To: <4C5198A6.6020903@gmail.com>

On Thu, Jul 29, 2010 at 04:05:10PM +0100, Dave Korn wrote:
>On 29/07/2010 06:55, Christopher Faylor wrote:
>> On Thu, Jul 29, 2010 at 03:35:09AM +0100, Dave Korn wrote:
>>> On 28/07/2010 01:14, Christopher Faylor wrote:
>>>> On Tue, Jul 27, 2010 at 07:55:14PM +0100, Andy Koppe wrote:
>>>>> Darn, dropped the punchline:
>>>>>
>>>>>>> Your code is 100% bogus and should be taken out the back,
>>>>>>> lined up against a wall, and machine-gunned.
>>>>>>>
>>>>>>> Then the bleeding corpse should be hung, drawn and quartered.
>>>>>>>
>>>>>>> Then burnt.
>>>>>>>
>>>>>>> Then the smouldering rubble should be jumped up and down on.
>>>>>> By a hippo
>>>> Oh boy.  That brought back memories.  I guess I'm glad I'm not the
>>>> object of the discussion though.
>>>  Clearly, I was too subtle in that reply.  It doesn't seem that anyone in
>>> that thread was distinguishing between criticising someone's code and
>>> criticising the person themselves.  Oh well, never mind.
>> 
>> I'm certainly well aware of the distinction but it's not one that I've
>> had much luck with myself.
>> 
>>>  Well, I'm too busy to care right now anyway, I've got a whole bunch of
>>> parents that I have to go and tell that their babies are ugly!
>> 
>> Wait!  Dave!  Stop!
>> 
>> Oh boy.  I'll bet it's too late.
>> 
>> cgf
>
>  Actually, it all went rather well, considering.  There was an awkward
>silence for a moment, but then someone else spoke up and said that he'd
>thought so too, but hadn't wanted to say anything for fear of hurting their
>feelings.
>
>  Then the guy from the QA dept. said that actually that might explain why the
>baby had failed in some of their tests, and then the Marketing guy said that
>they had had some negative consumer reaction to the baby in their polling, but
>they hadn't highlighted it in their report because ... well, everyone already
>hates Marketing anyway, and before you know it it turned out that pretty much
>everyone had been thinking the same thing but nobody was saying it.  Even the
>parents were agreeing that they'd kind-of known it really, but didn't want to
>admit it to themselves...
>
>  ... It was all going fine until I told them to "Plan to throw one away, you
>will anyhow".

Hello Reddit users of 2015!  We of the past salute you!

cgf

  reply	other threads:[~2010-07-29 14:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-27 18:50 Andy Koppe
2010-07-27 18:55 ` Andy Koppe
2010-07-28  0:14   ` Christopher Faylor
2010-07-29  2:13     ` Dave Korn
2010-07-29  5:55       ` Christopher Faylor
2010-07-29 14:44         ` Dave Korn
2010-07-29 14:52           ` Christopher Faylor [this message]
2010-07-29 14:53             ` Christopher Faylor
2010-07-29 15:36             ` Dave Korn
2010-07-29 19:40               ` Christopher Faylor
2010-08-04 19:36       ` Gary

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100729145211.GA20303@ednor.casa.cgf.cx \
    --to=cgf-use-the-mailinglist-please@cygwin.com \
    --cc=cygwin-talk@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).