re: Do you have a process for naming things? VIEW POST


1- Be consistent within your team or project
2- Names should describe why a programming element exists
3- Names should be pronounable, searchable, and without encoded info
4- Avoid numbers in names
5- Not too abstract, not too detailed


I feel like consistency is the most important thing. When you are done you can go about making things more readable / use better naming.

code of conduct - report abuse