Thanks for taking the time to reply, very valuable. Little tangent but in regards to the coupling/cohesion part; makes me wonder why some developers seem to ha

Thanks for taking the time to reply, very valuable. Little tangent but in regards to the coupling/cohesion part; makes me wonder why some developers seem to have no problem with accepting strict boundaries when dealing with third party (web) APIs they have no control over, they use parts of the interface they desire, they cherrypick/reduce the response content and create a separate model appropriate for their usecase/context and they tailor the behavior to that. This appears to go out the window to some extent when they do have control over the existing model and behavior. Far more appealing to use the model directly and modify or extend the behavior than to "needlessly" introduce some duplication in order to establish clear boundaries.