Human-readable classes & IDs for Javascript/CSS overrides

[jthoms]

I'm not a software engineer, so please forgive a potentially ignorant question:

How's the community handling the apparent move in the Canvas DOM towards less human-readable classes and IDs when doing CSS and Javascript overrides?

It may be just me, but I'm hesitant to target a class like ".tab-r1l_mqf4ag" or to crawl through the DOM (which seems to change from release-to-release). Up to this point, I felt empowered with my limited coding skills to work with clear classes and IDs, like ".add_module_item_link".

If I'm not the only one experiencing this discomfort, hopefully someone in the community can enlighten us.

[llawson]

Personally so far I have only had to grab element classes that only applied to specific pages (i.e.: login and confirmation buttons). I do this using Chrome's developer tools, but I am not sure where you would find a class cryptically named as such. Most of the element classes I have come across are conveniently named (menu-item, ic-app-header__menu-list-item, etc).

[James]

Student context cards are where I've encountered it ... so far ... but that's also one of the newest sections of code, so I know I am, and think people like  @jthoms  are, worried about what else is coming down the line that makes the system difficult to develop for.