Page 81 (Regulation by Code) - "The question here is not how the architecture of the Net will make it easier for traditional regulation to happen. The issue here is how...the code itself becomes a regulator... A locked door is not a command 'do not enter' backed up with a the threat of punishment by the state. A locked door is a physical constraint on the liberty of someone to enter some space."
"Code as a regulator" suggests that what can or cannot be done is increasingly being decided by programmers, application developers and Chief Information Officers. As a CIO, I sometimes half-joke that CEO's and CFO's don't really have any more power than we say they do. Through the applications themselves and IT policies / procedures we have the ability to limit the kinds of decisions possible, the type of information available and the speed in which it is received. It can often be very easy to say, "I'm sorry, the system doesn't allow that". Those with the technical knowledge increasingly have power to shape the environment and many will not know there was any other way.
Subscribe to:
Post Comments (Atom)
0 comments:
Post a Comment