>If he is an employee in our company, he will understand.

That's the tricky part. A good percentage of the architecture I do is related to the future and making sure what we do now will be easily understandable by the next one who will take over.

We never know what can happen inside the corporation list of employees and such. I have seen important changes happening in a flash. Then, everyone falls apart because they cannot understand what was done before. Whenever I revise the code of other resources, before approving them, I make sure that I can understand it and that it will be easy for someone new in the team to understand it at any given time. Yes, your thread is important. The naming convention we give to our classes, methods, properties and such is important. Standardization is also related. I am pretty sure you will come up with something that will properly reflect what this method does and can do in the future if it evolves.