Funnily enough, this is mistranslated. It means "beef labelling supervision (task) delegation law". The "regulation and" incorrectly changes the meaning, there are no regulations being defined per that word.
The mistake likely originates from the full name of this law, "Rinderkennzeichnungs- und Rindfleischetikettierungsüberwachungsaufgabenübertragungsgesetz", where the first part is "cow* labelling and…"
* Live animals, only the 2nd part is about meat products.
(It was all about tracking the origin of meat products, was a state law in one of the federal states of Germany, and was in force from 2000 until 2013.)
P.S.: there is some fancy hyphenation happening in that word! Make your window narrower ;D
For example [1] lists Rindfleischetikettierungsüberwachungsaufgabenübertragungsgesetz abbreviated as RflEttÜAÜG. I've receently had to deal with some German forms and after introducing the abbreviation in the first paragraph, the applicable law is usually referred to by that abbreviation.
1: https://de.wikipedia.org/wiki/Rindfleischetikettierungs%C3%B...
For the first two words, a couple of additional consonants from the body of the word are added, to reduce ambiguity.
These seem like sensible rules.
oyster_results.filteredMAF0.05_filteredHWE0.05_etc._pp_.vcf.gz
I stopped doing that once I learned about file system-specific filename length limits...
Class names are a separate discussion.
The problem with long var names is that formulas become unreadable and function names take away horizontal real estate for their args.
There are so many ways out to make it shorter yet readable.
- idx is often used as index.
- An event handler can start with On.
- Simply take the first 3 or 4 letters of every word. simpToReadVar
- keyISR Keyboard Interrupt Service Routine
- fName file name
I've seen code that named classes and variables much worse than that.