Evolving software under constrained resources is a challenge, and I think we kid ourselves when we don't admit this. Software that is providing value often grows in scope until it is a mess. Today I talk to Wade Waldron about how avoid this situation or recover from it.
Big ball of mud is the title of a paper presented at the 1997 Patterns Languages of Programs conference and I think it is super interesting.
The researchers went out into the field to see what architectures software in industry were following. Big Ball of mud is what they found, along with other 6 other patterns with names like "sweep it under the rug" and reconstruction, which is the throw it away and start again pattern.
Check out other episodes like this Philip Wadler:
This podcast originally published here :