Re: Source code security - rogue developers?

From: Bill Turner (510048981350-0001NoNoNo@t-online.de)
Date: 06/17/02 

From: Bill Turner <510048981350-0001NoNoNo@t-online.de>
Date: Mon, 17 Jun 2002 22:54:15 +0200

Kevin Cline wrote:

> My recommendation is that you focus on hiring trustworthy people, and
> then trust them.

I couldn't agree more. Personally, I wouldn't want to work in an organization were I was not trusted. Sure, there
maybe special cases, such as military or CIA or the like. Even then, the code itself is not likely terribly
valuable. Also, I like to read code. I see something others are doing, think that it could be useful now or in the
future, or just think what they have done is cool, and want to know more about it. Not being able to look at other
code would be extremely frustrating.

Bill

Relevant Pages

  • Re: Source code security - rogue developers?
    ... Kevin Cline wrote: ... > My recommendation is that you focus on hiring trustworthy people, ... > then trust them. ...
    (comp.security.misc)
  • Re: Can this be done by Group Policy?
    ... For a lab environment, this is probably fine. ... recommendation in the context of a large organization in a production ... pointing to specific directories to make Full Trust, ... > and run projects with Visual Studio in their own My Documents folders ...
    (microsoft.public.dotnet.security)
  • Re: concerned and confused about adding shadow-set members to system disk
    ... If VMS reboots and expects, ... > Where is this recommendation spelled out? ... >> Simply put, if you trust your hardware then use the first method, if you ...
    (comp.os.vms)
  • Re: Best book on learning C++?
    ... > recommendation specified right there in the entry. ... reviewer recommends a rating, then usually, the rating is given. ... trust the reviewers on there as they know what they're talking about. ... Schildt does have a very good ...
    (alt.comp.lang.learn.c-cpp)
Loading