Using Strategy & Function-Specific To Attack Large Classes

In IT work — "it puts the database on its browser skin" — we often face sooner or later the problem of the gigantic object. Some systems, especially "global monolith reboots", just start there. Others just grow and grow and insensibly slide into it over time. The problem is that there are one or a few objects that are just plain central to the domain. To forestall ron and his marick quote, I’ll use the classic ‘order’ as my example …

Using Strategy & Function-Specific To Attack Large Classes Go to Post »