Naming #1 — Naming from inside vs naming from outside

💡Naming a function or a class in software can be approached from either the inside out or the outside in.

Inside-out means that we look to what the code of the function/class is doing and we try to put a name in that by resuming instructions to a compact concatenation. That’s crap 💩 🤮

❓Let’s take the example in the image:
A public method in a Display class named inside out.

❌That function doesn’t express the intent of the caller. Instead it make the client code less readable by twisting useless details in the orchestration code.

✅As an alternative, “Display.write(message)” is more expressive , free from implementation details and will better resist refactoring the code inside the function in the future.

👌🤓Using the outside-in approach in naming functions can make code more readable, as it gives an idea of what the function is supposed to do, regardless of how it is implemented.