Why Software Becomes a Big Ball of Mud

If you’ve worked on any software projects that involved “legacy” code, you’ve probably had the sense at times that you were working with a “big ball of mud” and felt the constant low-grade terror that goes with that experience. Unfortunately, poorly coded software architecture seems to be the most frequently deployed pattern around. In this week’s post over at Press Up, David explains how things get so muddy in the first place so you can tackle your legacy code more effectively.


Add a Comment

Your email address will not be published. Required fields are marked *