We have been using the term ever since. The term itself, in turn, appears to have arisen during the '70s as a characterization of Lisp . Grandiose flights of architectural fancy weren't possible, which reduced the number of design alternatives that could be put on the table. One of mud's most effective enemies is sunshine. Subjecting convoluted code to scrutiny can set the stage for its refactoring, repair, and rehabilitation.
Code reviews are one mechanism one can use to expose code to daylight.
A pure pair programming approach requires that every line of code written be added to the system with two programmers present. In contrast to traditional solitary software production practices, pair programming subjects code to immediate scrutiny, and provides a means by which knowledge about the system is rapidly disseminated. Sunlight, it is said is a powerful disinfectant. Pair-practices add an element of performance to programming. An immediate audience of one's peers provides immediate incentives to programmers to keep their code clear and comprehensible, as well as functional.