On Thu, 18 Nov 2010 12:48:19 -0500, David Lamb wrote:
> On 18/11/2010 12:09 AM, ClassCastException wrote:
>> On Wed, 17 Nov 2010 22:26:42 -0500, Arne Vajhøj wrote:
>>
>>> On 25-10-2010 00:39, ClassCastException wrote:
>>>> On Sun, 24 Oct 2010 15:25:20 -0400, Arne Vajhøj wrote:
>>>>
>>>>> On 24-10-2010 07:58, ClassCastException wrote:
>>>>>> On Sat, 23 Oct 2010 21:12:58 -0400, Arne Vajhøj wrote:
>>>>>>
>>>>>>> On 23-10-2010 02:49, ClassCastException wrote:
>>>>>>>> You can not do anything to protect against another developer
>>>>>>>> using a non standard extension. 
>>>>>>>
>>>>>>> Ever heard of code review?
>>>>>>
>>>>>> So, maybe your boss can. You still can't. 
>>>>>
>>>>> Why do you think it is called peer review and not boss review?
>>>>
>>>> You didn't say "peer review", you said "code review".
>>>
>>> Code reviews are supposed to be peer reviews.
>>
>> "Supposed to be" being the operative words here.
>
> Arne is using the phrase in its original, technical sense -- the one I'd
> expect to be the default on a programmer's newsgroup. IIRC the early
> literature on code reviews found it is significantly less effective if
> there is any suspicion it's also being used as personnel review. Just
> because your boss calls it a code review doesn't make it one.
All of this is wandering pretty far from the original point, which is
right at the top of the quoted material:
>>>>>>>> You can not do anything to protect against another developer
>>>>>>>> using a non standard extension.
If your boss reviews code he can. If your institution imposes peer review
of code, then maybe you can. If your institution doesn't, it's again on
your boss to maybe change that, though.