re: When do you create a function or method? VIEW POST

VIEW FULL DISCUSSION
 

My primary goals are:

  • readability - by being so expressive as possible and use short methods
  • hiding details - by using private methods for them
  • avoiding duplicities - by moving that code to reusable method
 

That's a great list so far.

What do you think about maintainability? Should you be reducing the amount of methods or functions you create to help maintainability?

 

You mean 10 longer methods instead of 20 shorter? Or something else?

Yes, too many can become a headache when trying to find if a functionality has already been implemented or simply when trying to debug a function, it's quite difficult to retain a lot of function calls.

It's really hard to tell. It's more like a process from less and longer methods (and less classes) to more and shorter, until its feels right.

How to find what was implemented? Put things on right place. So proper domain modelling, group helper methods to helper classes

I often think about methods in layers - public method is first layer. Do I need to check what called private methods do? Not so often.

code of conduct - report abuse