GO CONVENTION
Go Naming Conventions: Avoid the ‘What’s This?’ in Every Code Review
Go Naming Convention is especially important for larger projects where multiple developers may be working on the code simultaneously…
Sticking to naming conventions really does matter. When done right, it makes your code clear and easy to update and it’s even more crucial in bigger projects where many developers are involved.
It ensures that everyone, whether a newbie or a pro, can dive in, understand and contribute.
Before we dive in, it’s important to remember that conventions come from team decisions.
Changing them just because you’ve heard some new ideas might not always be best and what really makes conventions effective is everyone on your team, or in your company, being consistent.
So, if you think about making changes, always talk to everyone and get their input
1. Package Naming
lowercase
When you’re deciding on a package name, always use lowercase. If you find yourself with a two-word name, simply put them together without adding dots or underscores.
