I don’t like your technique because: 1- As you say yourself, there is some amount of subjectivity about when « handleX » is the best description (when the effe

I don’t like your technique because: 1- As you say yourself, there is some amount of subjectivity about when « handleX » is the best description (when the effect is extensive enough) and when it is not. 2- The whole point of calling handlers « handleX » is that you DO get to know what happens when the event X happen: you just have to read the content of « handleX » function. So here is my solution: follow conventions. If your handler is a simple thing like « setServer » you’ll see that the function content is one line of code. If it’s more complex, you will see it also. It works 100% of the time, ensures that people won’t loose their mind reading your code, and prevent useless debates about form.