Still, this approach endures and thrives. Why is this architecture so popular? Is it as bad as it seems, or might it serve as a way-station on the road to more enduring, elegant artifacts? What forces drive good programmers to build ugly systems? Can we avoid this? Should we? How can we make such systems better?
An experiment in weblogging by the Yantis' of Temecula.
Things we find interesting. Items including (but not limited to) Temecula, the Yantis family, literature, technology, science, computers, the Internet, horses, and teaching. Items will be added to this weblog as we find them. With luck and time there will be new things to read about every day, so check back with us frequently. Posts not currently on the main page are available in the archive. Established December 6, 1999
Friday, July 27, 2001
Big Ball of Mud... A BigBallOfMud">BIG BALL OF MUD is haphazardly structured, sprawling, sloppy, duct-tape and bailing wire,
spaghetti
code
jungle.
We’ve all seen them.
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.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment