"Richard Heathfield" <rjh@see.sig.invalid> a écrit dans le message de news:
fMydnRETGIuBUJLanZ2dneKdnZydnZ2d@bt.com...
> Mark McIntyre said:
>
>> On Fri, 12 Oct 2007 17:43:30 +0000, in comp.lang.c , Richard
>> Heathfield <rjh@see.sig.invalid> wrote:
>>
>>>Tor Rustad said:
>>>
>>>> I rather prefer to train a smart junior,
>>>> than to change the mindset and attitude of a senior.
>>>
>>>Yes, I can understand that - but on the other hand, obviously I don't
>>>think there's anything wrong with my mindset and attitude, because
>>>otherwise I'd change it myself. And *I* would change it. It's not your
>>>job to change my mindset.
>>
>> Unfortunately thats *precisely* the sort of arrogance that one can't
>> afford.
>
> Well, it's not actually arrogance. The point is that my mind is *my* mind,
> not *your* mind. If you want to hire it, fine. But *changing* it is my
> prerogative, just as changing your mind is your prerogative.
>
>> If someone isn't open to having their mindset changed by
>> others, then they're probably useless as an employee. Imagine if you
>> hired someone who refused point blank to change to your in-house
>> coding standard, or to use your in-house libraries....
>
> The trick is to review the coding standard during your first day, and come
> up with a long list of proposed changes (which, naturally, you will be
> prepared to justify). Once you've won that battle, you can start in on
> reviewing the in-house libraries. :-)

I would be very interested to see your coding standard.

--
Chqrlie.

Charlie Gordon said:

> "Richard Heathfield" <rjh@see.sig.invalid> a écrit dans le message de
> news: fMydnRETGIuBUJLanZ2dneKdnZydnZ2d@bt.com...
>> Mark McIntyre said:
>>
<snip>
>>> If someone isn't open to having their mindset changed by
>>> others, then they're probably useless as an employee. Imagine if you
>>> hired someone who refused point blank to change to your in-house
>>> coding standard, or to use your in-house libraries....
>>
>> The trick is to review the coding standard during your first day, and
>> come up with a long list of proposed changes (which, naturally, you will
>> be prepared to justify). Once you've won that battle, you can start in
>> on reviewing the in-house libraries. :-)
>
> I would be very interested to see your coding standard.

No, you wouldn't. :-) Seriously, I don't have one, in the formal document
sense. Never saw the point.

On site one can't, diplomatically speaking, get away with "your coding
standard is rubbish, use this instead" on one's first day, whereas one
very often /can/ get away with "your coding standard makes for an
interesting read, but I've identified the following problems with it, and
I've added explanations of why they are problems, along with suggested
solutions, what do you think?". So the modifications that one suggests
will differ from site to site, making a single master document less useful
than it might otherwise be.

And for my own code, my coding standard is of course in my head. Is it
worth writing down? Maybe, maybe not.

--
Richard Heathfield <http://www.cpax.org.uk>
Email: -http://www. +rjh@
Google users: <http://www.cpax.org.uk/prg/writings/googly.php>
"Usenet is a strange place" - dmr 29 July 1999