anchor.diff:  
   
   [quote, Tim Mickinnon, from Mock Roles Not Objects (2004)] 
  -
  -__The trigger for our original discovery of the technique was when John Nolan set the challenge of writing code without getters. Getters expose implementation, which increases coupling between objects and allows responsibilities to be left in the wrong module. Avoiding getters forces an emphasis on object behaviour, rather than state, which is one of the characteristics of Responsibility Driven Design.__  
  - 
  +__The trigger for our original discovery of the technique was when John Nolan set the challenge of writing code without getters. Getters expose implementation, which increases coupling between objects and allows responsibilities to be left in the wrong module. Avoiding getters forces an emphasis on object behaviour rather than state, which is one of the characteristics of Responsibility Driven Design.__
    
   
   
  
positive.code: 
  
  
  ====== Implementation Using A Tell Approach
  
  The **Tell** is all about telling an object to perform some piece of work on your behalf rather than asking that object for data and then doing the work yourself. In the previous example, the protocol converter asked another object for the message concatenation info and then added those parts itself to the message. In the following example, we ask another object to do this bit of work for us. Firstly we introduce a domain object to replace the map use for the multipart parameters:
  
  
negative.code: * The part number of the message
  * Total number of parts for the message
  
  
  ===== Implementation Using An Ask Approach
  
  
  A factory was used to create a map of parameters for message concatenation:
  
  