Re: read-only checkout when developer has no commit access

On Tue, 25 Jul 2000, Jonathan S. Shapiro wrote:
> Okay. This is a usability call. A case can be made for both interfaces. The
> difference in philosophy is that you are trying to protect the idiots from
> damaging themselves while I am trying to take the view that files in my
> workspace are mine to do with as I wish.

I take the view that the philosophy that "idiots should be _protected_
from damaging themselves" is one of the most poisonous attitudes a
software developer can take. Certainly the tool should encourage the
correct behavior, but it should get out of the way, and quickly, when
developers have even an inkling of knowing what they're doing.

Images of someone going "I checked it out and, since the tool let me
modify it locally, why won't it let me check it in?" reminds me of the "my
brain hurts!" skits on Monty Python. =)

        Brian
Received on Sat Oct 21 14:36:06 2006