To novice, most of these are guidelines, don't treat them as rules. If something feels wrong to you, you are free not to follow them. Also almost always follow

To novice, most of these are guidelines, don't treat them as rules. If something feels wrong to you, you are free not to follow them. Also almost always follow the conventions of your team/project. Nothing is worse than multiple coding styles in a project, unless whole team finds it better and decides to follow it. Clear naming will give you most ROI. When you have confusion follow the simplest path, it is always easier to refactor simple code later.