Patterns without Purpose


that aren't adding significant value. The real key is to avoid trying to spell out the use of every pattern before you know what you really need. Instead, if you're able to continually inspect and adapt your architecture, you'll be in a much better position to strike a balance between what is needed and what is simply another useless layer.

About the author

Tod Golding's picture Tod Golding

Tod Golding is the founder of Blue Puma Software, a technical consulting company that provides software training, mentoring, and development services. He has twenty years of experience as a software developer, lead architect, and development manager for organizations engaged in the delivery of large-scale commercial and internal solutions. Tod has an extensive background leveraging .NET, J2EE, and Windows DNA technologies, which has allowed him to become equally skilled with C#, Java, and C++. He has worked and consulted at a variety of companies, including stints with Microsoft and Borland. Tod is the author of Professional .NET 2.0 Generics and a contributing author for the XML Programming Bible. Tod can be contacted at

AgileConnection is one of the growing communities of the TechWell network.

Featuring fresh, insightful stories, is the place to go for what is happening in software development and delivery.  Join the conversation now!