Variables, as opposed to notation, tend to be local in scope, so 1) it isn't vital to have a memorable name and 2) it wouldn't really help to have a 'proper' name, either. As an example, if we're talking about two elements from a group, we usually talk about two elements, a and b, in a group, G. Could you call them elements 1 and 2 from an ExampleGroup? Maybe, but there's no clarity provided since these variables are only scoped for a given section. Additionally, longer equations means that it takes longer to read through and check steps like algebraic manipulation in a proof, or application of a lemma or theorem.
What is globally scoped are things like theorems, lemmas, definitions, etc., and those are easy to track down since they are by convention numbered after chapter and section.
I've basically abandoned all languages/ecosystems that aren't, at the very least, extremely grep-friendly. Static types preferred so I can get that sweet, sweet auto-refactoring, jump-to-references/definition, docs-on-hover, et c.
If we expected people to read code like they're expected to read math, I'd have taken the huge pay hit and left the profession by now. It'd be a choice between that or a spiral into depression ending in tragedy. I don't know how math-loving folks can stand it.