It is a question of the relationship between the execution time of the method and the number of calls. The call to a method is not neutral, but is relatively fast. On the other hand, if the number of calls of this method is high, then the impact in terms of performance may be very high.
It is also important to measure the impact of splitting methods regarding the database engine queries in a Client/Server environment. If this split generates a greater number of exchanges between client and server, it may be disadvantageous to do so because it will have a significant impact in terms of latency and will disproportionately slow down the execution of your application.
Naming convention will help to be more in control.
Use the Macro to enhance your productivity.
Before to start implementing any code in your target application, do a simple database first to test your code and your idea. This way you will have a much better control, you will be able to better test and isolate any issues without risk of side effects related to your target application.
Code review with a 4D expert is also a very good way of enhancing your skills.
Embrace rather than fight
My main recommendation is to follow 4D’s development principles and not to try to apply your technical habits inherited from other environments.
I’ve seen too many projects failing because programmers were trying to apply their practices inherited from C#, JAVA, PHP, etc… to 4D.
It’s like you decide to swim against the waves. You’ll exhaust yourself and eventually drown. On the other hand, if you decide to surf the wave…