C#

RobCroll wrote:

pull on the cowboy boots

RobCroll wrote:

An example I clearly remember was a situation where a number of methods were passing many parameters and requesting the same data multiple times. By encapsulating the parameters, the methods became a lot more maintainable and only had to do the work once. This is not something an architect is in a position to envisage.

call ClassLib1.DoStuff(a, b, c, d)
      getData e, f, g, h.
      call ClassLib2.DoMoreStuff(a, b, c, d, e)
                 getData i, j, k, l.

      call ClassLib3.EvenMoreStuff(a, b, c, d, e, f)
                 getData i, j, k, z //Hang on we already got most of this in DoMoreStuff


So instead:
aClass = new aClass() //Add a, b, c, d
ClassLib1.DoStuff(aClass)
      getData e, f, g, h.
      //Add e, f, g, h to aClass
      
      call ClassLib2.DoMoreStuff(aClass)
                 getData i, j, k, l.
                 //Add i, j, k, l to aClass

      call ClassLib3.EvenMoreStuff(aClass)
                 //don't need to getData i, j, k we already have it
                 getData z 
                 //Add  to aClass

Debug.WriteLine(@"Current Thread ID: " + System.Threading.Thread.CurrentThread.ManagedThreadId.ToString());