Question

What do you do when you notice that an app has a lot of classes, but the classes are not really intantiable objects but rather a grouping of common functions?

Example:

Class Point  {   calculatePoints(something) {}   calculatePointsAnotherWay(something) {}  } 

Answer 1

I’d look at the functions to see how they are using instantiable objects. If a function:

• takes an object of a user-defined type as an argument,
• extracts data from that object, and
• produces a result based on computations over those extracted data,

then that function is a candidate for becoming a method on the class of its argument. This kind of coding is sometimes a clue that the programmer who created the original type or the programmer who wrote the ‘external’ function (or both) may still be thinking in imperative/procedural style, rather than OO style.