Bozo bit

In early versions of Apple's Macintosh Operating System, the bozo bit was one of the flags in the Finder Information Record, which described various file attributes. When the bit was set, the file could not be copied. It was called the bozo bit because it was copy protection so weak that only a bozo would think of it, and only a bozo would be deterred by it. After Mac OS Version 4.0, the Finder ignored this bit. [cite book | last = Chernicoff | first = Stephen | title = Macintosh Revealed, Volume One: Unlocking the Toolbox | publisher = Hayden Book Company | location = Indianapolis | year = 1987 | isbn = 0672484005]

The notion of the bozo bit was adopted by [http://www.mccarthyshow.com/ Jim McCarthy] in his 1995 book "Dynamics of Software Development" (ISBN 1-55615-823-8), which presented a series of rules about the political and interpersonal forces that drive software development. At the time, it's fair to say that most coders still thought of themselves as technology experts first, team members second. The technical issues facing programmers were sufficiently daunting that just getting code written was commonly considered good enough; McCarthy and other authors (Lister & DeMarco, Constantine, McConnell, Ed Sullivan (ISBN 0-7356-1184-X)) were just breaking the news that social issues trump technical ones on almost every project.

Rule #4 is "Don't Flip The Bozo Bit". Bozo the clown was a figure of fun, someone certainly not to be taken seriously. McCarthy's advice was that everyone has something to contribute--it's easy and tempting, when someone ticks you off or is mistaken (or both), to simply disregard all their input in the future by setting the "bozo flag" to TRUE for that person. But by taking that lazy way out, you poison team interactions and cannot avail yourself of help from the "bozo" ever again.

External links

* [http://c2.com/cgi/wiki?SetTheBozoBit Setting the Bozo Bit as an Antipattern]

References