I do the same. Usually, in a professional setting, you're working with something like JIRA so it makes sense to prefix a branch with a ticket (as a way to say "this branch is related to this story") and then a short human-readable description of the feature.
As a general rule of thumb, if your brain has to pause and make sense of a branch name, it's too complex.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.