Big Ball Of Mud: Difference between revisions
it's "baling wire" |
|||
Line 1: | Line 1: | ||
'''The Big Ball Of Mud''' is the most prevalent [[software architecture]], according to Brian Foote and Joseph Yoder of the Department of Computer Science at the University of Illinois at Urbana-Champaign. |
'''The Big Ball Of Mud''' is the most prevalent [[software architecture]], according to Brian Foote and Joseph Yoder of the Department of Computer Science at the University of Illinois at Urbana-Champaign. |
||
"A Big Ball of Mud is a haphazardly structured, sprawling, sloppy, [[duct tape|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." |
"A Big Ball of Mud is a haphazardly structured, sprawling, sloppy, [[duct tape|duct-tape]]-and-baling-wire, [[spaghetti code|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." |
||
However Foote and Yoder do not condemn big ball of mud programming and indeed point out that this form of programming is most prevalent because it works. |
However Foote and Yoder do not condemn big ball of mud programming and indeed point out that this form of programming is most prevalent because it works. |
Revision as of 19:45, 20 September 2002
The Big Ball Of Mud is the most prevalent software architecture, according to Brian Foote and Joseph Yoder of the Department of Computer Science at the University of Illinois at Urbana-Champaign.
"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."
However Foote and Yoder do not condemn big ball of mud programming and indeed point out that this form of programming is most prevalent because it works.