Big ball of mud
This article needs additional citations for verification. (May 2020)
A big ball of mud is a software system that lacks a perceivable architecture. Although undesirable from a software engineering point of view, such systems are common in practice due to business pressures, developer turnover and code entropy. They are a type of design anti-pattern.
In computer programs
A Big Ball of Mud is a haphazardly structured, sprawling, sloppy, duct-tape-and-baling-wire, spaghetti-code jungle. These systems show unmistakable signs of unregulated growth, and repeated, expedient repair. Information is shared promiscuously among distant elements of the system, often to the point where nearly all the important information becomes global or duplicated.
The overall structure of the system may never have been well defined.
If it was, it may have eroded beyond recognition. Programmers with a shred of architectural sensibility shun these quagmires. Only those who are unconcerned about architecture, and, perhaps, are comfortable with the inertia of the day-to-day chore of patching the holes in these failing dikes, are content to work on such systems.— Brian Foote and Joseph Yoder, Big Ball of Mud. Fourth Conference on Patterns Languages of Programs (PLoP '97/EuroPLoP '97) Monticello, Illinois, September 1997
Foote and Yoder have credited Brian Marick as the originator of the 'big ball of mud' term for this sort of architecture.
Programmers in control of a big ball of mud project are strongly encouraged to study it and to understand what it accomplishes, and to use this as a loose basis for a formal set of requirements for a well-designed system that could replace it. Technology shifts, such as client–server to web-based or file-based to database-based, may provide good reasons to start over from scratch.
In relation to Lisp
In discussion of the Lisp programming language the term big ball of mud is used differently, in this case to describe the malleability of a Lisp system. In Lisp, it is generally possible to:
- Easily write macros that give control over the language syntax, so that the notation looks closer to the problem's domain
- Use a data-directed programming style
- Execute parts of a program at compile time rather than runtime
- Save a system image of a modified Lisp implementation for future use
As a result of the confluence of these features, Lisp is extraordinarily flexible, even to such an extent that the language implementation itself may be completely rewritten during runtime (i.e. reflective metaprogramming), which can result in Lisp systems becoming "muddy" over time due to the fluidity and ease with which they may be extended and evolve through simple use. Metalinguistic abstraction, a prominent characteristic of Lisp, also allows programmers to develop entirely new and idiosyncratic conceptual vocabularies to describe the processes and functions their programs go through in tackling a problem domain, and can, if combined with poor software documentation, result in Lisp systems that work quite well and are indeed quite well-structured from a design perspective, but are only comprehensible to the original coders, or to anyone else willing to invest the time to sift through layers of highly recursive code.
APL is like a beautiful diamond – flawless, beautifully symmetrical. But you can't add anything to it. If you try to glue on another diamond, you don't get a bigger diamond. Lisp is like a ball of mud. Add more and it's still a ball of mud – it still looks like Lisp.
- Foote, Brian; Yoder, Joseph (26 June 1999). "Big Ball of Mud". laputan.org. Retrieved 14 April 2019.
- Richard P. Gabriel and Guy L. Steele (1996). "The Evolution of Lisp". ACM History of Programming Languages—II. 28 (3): 233–330. doi:10.1145/155360.155373.
- Thomas J. Bergin and Richard J. Gibson (1996). "Supplemental material from HOPL II". ACM SIGPLAN Notices. 31 (11): 9–20. doi:10.1145/240964.1198155.