It's a strange game. The only winning move is not to play.

This quote is very relevant for my career progression:

>Within a month of his arrival, Randy solved some trivial computer problems for one of the other grad students. A week later, the chairman of the astronomy department called him over and said, “So, you’re the UNIX guru.”

>At the time, Randy was still stupid enough to be flattered by this attention, when he should have recognized them as bone-chilling words. Three years later, he left the Astronomy Department without a degree, and with nothing to show for his labors except six hundred dollars in his bank account and a staggeringly comprehensive knowledge of UNIX.

Maybe people can help in other ways you don't anticipate.

* Similar to encodings and locales: Variation in line endings, path separators, command line quoting, case sensitivity

* OS and language-specific package management

* CI/CD

* VMs, containers

* Licenses

Having colleagues for who this topic is "daily business", I really don't know what you intend to teach about this topic to computer science students:

It's either

- basically trivial: you use the provided exchange rate tables which can vary from day to day; you thus just have to thoroughly pay attention concerning the exchange rates of which day you have to use for a given calculation (but this is something the business people will tell you), the rest is like unit conversion, which you learn in school: If the "exchange rate" between yards and inches is 36 in/yd, then 2.5 yd = 2.5 yd * 36 in/yd = 90 in. Similarly, if the f/x rate that is to be used is 1.1612 USD/EUR, then 2.50 EUR = 2.5 EUR * 1.1612 USD/EUR = 2.903 USD (you now just need to ask the business people whether they want to use this raw result, or the result is to be rounded. In the latter case, they will tell you which kind of rounding they want).

- or it is something that you rather need to become an auditor (or a similar qualification) for.