Most of the time we try to use English for technical identifiers and German for business langugage, leading to lets say "interesting" code, but it works for us.
Most of the time we try to use English for technical identifiers and German for business langugage, leading to lets say "interesting" code, but it works for us.
The Donau is a river. On this river is a steamship (Dampfshiff): Donaudampfschiff
This ship is part of an organisation (Gesellschaft) that manages cruises (Fahrt): Donaudampfschifffahrtsgesellschaft
The ship has a captain (Kapitän) who has a cap (Mütze): Donaudampfschifffahrtsgesellschaftskapitänsmütze
On this cap is a button (Knopf): Donaudampfschifffahrtsgesellschaftskapitänsmützenknopf
You could extend this example: The button is colored with a special paint (Farbe), which is produced in a factory (Fabrik): Donaudampfschifffahrtsgesellschaftskapitänsmützenknopffarbenfabrik
And the factory has an entry gate (Eingangstor): Donaudampfschifffahrtsgesellschaftskapitänsmützenknopffarbenfabrikeingangstor
In English, this would be a huge sentence, all in reverse order: The entry gate of the factory that produces the color for the button on the captain's cap of the ship belonging to the cruise organization on the Donau.
The German is a lot more compact, if sometimes hard to parse :-)
Anyway, there is also a perfectly acceptable and established way of making German words easier to parse if need be: hyphens. So Hyphen-Case instead of PascalCase.
I’m sure a native German speaker wouldn’t make the same mistake, though.
"Selbständig" (freelancing) is obviously derived like self-standing, but "selb" is archaic and completely unused, prompting native learners to write 'selbstständig, which is wrong.
Couple more ones like this. Ask a native speaker about hinüber vs herüber, they will be perplexed, because it feels so dialectal. And nobody even knows about imperfect tense vs perfect tense, it's just stylistics to most.
Not anymore: