It is aptly titled, The Big Ball of Mud. And it is, appropriately enough, an essay about the most commonly used design pattern. You might expect that it is about how horrible it is to have a mess. But there is more here than that. Rather it is about how messes arise, what messes do right, what you can do about them, and what you can learn from them. (Which is a lot more than might think.)
If you have never worked in a big ball of mud, and your code would never evolve into one, then there is no point in your reading this. You either lack the experience needed to put the points made into a proper context, or else you are not a mere mortal like myself. But if you are an experienced mortal, you may find it worth the read.
UPDATE
Oops, big ball, not great ball. *blush* (I left the
title alone.)
|
---|
Replies are listed 'Best First'. | |
---|---|
Re: Big Ball of Mud
by dws (Chancellor) on Nov 11, 2001 at 09:01 UTC | |
Re: The great ball of mud
by mitd (Curate) on Nov 11, 2001 at 13:18 UTC | |
Re: The great ball of mud
by brianarn (Chaplain) on Nov 12, 2001 at 23:03 UTC | |
Re: The great ball of mud
by princepawn (Parson) on Nov 17, 2001 at 18:25 UTC |