I'm just throwing my 2 cents in behind CamelCase with the occasional underscore, if they let you. It really helps to check with your programming team and work out a convention early on. They usually have a very specific standard that they adhere to and generally would be pretty happy if you stuck to it. Or they will work…
It's just a standard that works. It's so drilled into my head that I use it for every single file on my computer. :) Naming conventions are extremely important in an involved project or pipeline that might have 1000s of files and dozens or even 100s of team members. It's easy to understand and helps visually break an asset…