Bozo bit

The term bozo bit has been used in two contexts. Initially a weak copy protection system in the 1980s Apple classic Mac OS, the term "flipping the bozo bit" was later reused to describe a decision to ignore a person's input. It is a whimsical term, possibly derived from the classic children's comedy character, Bozo the Clown.

Weak copy protection

In early versions of Apple's classic Mac OS, the "bozo bit" was one of the flags in the Finder Information Record (also called the "no copy" flag in some documentation), 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 System 4, introduced in early 1987, the Finder ignored this bit.[1][2]

The cassette and ROM filing systems[3] and the Advanced Disc Filing System[4] of Acorn MOS feature a rudimentary copy protection mechanism where a file with a certain flag set cannot be loaded except to execute it.

The Compact Disc has a similar "no copy" bit in the subcode, but nearly all disc-copying software ignores it, and usually removes it on copies. Consumer-grade dedicated hardware audio disc copiers usually honor the bozo bit, and will refuse to copy a disc with the bit set. Professional disc copiers ignore the bozo bit and will copy a protected disc.

Dismissing a person as not worth listening to

In his 1995 book Dynamics of Software Development[5], which presented a series of rules about the political and interpersonal forces that drive software development, Jim McCarthy applied the bozo bit notion to the realm of human interaction.[6][7] 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) were just breaking the news that social issues trump technical ones on almost every project.

McCarthy's Rule #4 is "Don't Flip The Bozo Bit". McCarthy's advice was that everyone has something to contribute – it's easy and tempting, when someone ticks a person 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, the person poisons team interactions and cannot avail themselves of help from the "bozo" ever again.[6]

gollark: Having an option "websocket or TCP" and then a few `match`es to handle that would be MUCH EASIER than a plugin API.
gollark: Rust has TONS of decent scripting languages.
gollark: You could, in fact, just have some sort of "config file".
gollark: Do you plan to have other people make plugins ever?
gollark: <@738361430763372703> reject plugin systemreturn to recompiling code on changes

See also

References
  1. Chernicoff, Stephen (1987). Macintosh Revealed, Volume One: Unlocking the Toolbox. Indianapolis: Hayden Book Company. ISBN 0-672-48400-5.
  2. Stephen L. Michel (1988). IBM PC and Macintosh networking. Hayden Books. p. 10. ISBN 9780672484056.
  3. Bray, Andrew C.; Dickens, Adrian C.; Holmes, Mark A. (1983). The advanced user guide for the BBC Microcomputer. Cambridge: Cambridge Microcomputer Centre. p. 347. ISBN 0-946827-00-1. Archived from the original (zipped PDF) on 2006-01-14. Retrieved 19 April 2012.
  4. "5. The filing system commands". The Advanced Disc Filing System user guide (PDF) (1st ed.). Acorn Computers. August 1985. p. 32. Retrieved 19 April 2012.
  5. McCarthy, Jim (July 1, 1995). Dynamics of Software Development. Microsoft Press. ISBN 1556158238.
  6. Ronald J. Leach (2000). Introduction to software engineering. CRC Press. pp. 61–62. ISBN 9780849314452.
  7. Paul Glen and David H. Maister (2002). Leading geeks. John Wiley and Sons. pp. 37. ISBN 9780787961480.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.