You said "An application object that has many methods is not a good thing IMO"

Could you elaborate on your point here?





>>Hi,
>>We have 3 developers in a team. We need to work on the same class but different method in a project.
>>
>>What is the best approach to do this? Should we allow multiple checkout of source control or other better ideas?
>>
>>Thank you
>
>A class is supposed to have a clearly defined purpose. Code normalization! Usually the methods of that class support it in doing that purpose. That decreases the chance that multiple developers would need to work on different methods at the same time.
>
>In other words, you may have a class that has multiple purposes. You could reengineer it. An application object that has many methods is not a good thing IMO. However if that object instantiates many other objects it can provide many purposes at runtime and be maintainable by many programmers at design time.