I'm a software engineer (not in games or animation) and I typically work in medium teams where reading is more common than writing, and it's fascinating to me that these conventions you list are almost identical to what I'd ask any of my team members do in almost any language!
I usually explain it to newcomers as "Coarse to fine" sorting, I.e., biggest thing first, then smaller as you go. Very amusing to see something similar happen here too. Although, there is one key difference which is that abbreviations can really stack up and make things difficult, so I jokingly have a rule called AAAE (All Abbreviations/Acronyms Are Evil)
Thank you for explaining this so well!
Wayne is like the Superman version of explaining. Only he wont wait until a billboard that detached from a building roof is falling from the sky while you're walking by and you suddenly realize it's about to hit you, but then it stops, inches above your head, and then you realize you've been saved by him. No no, Wayne will make a video guide of the city pointing out Billboard dangers zones for you to avoid and he'll make you a list of phone numbers for emergencies. And if you decide to go visit anyways and get into trouble, he'll be there to save you nonetheless.