Normally I'll read and write any programming related documentation in english, since it's easier to share, refer to common terms and concept, lookup online, etc, and every dev is expected to be able to read it anyway (else they'll have much worse troubles with error messages, tooling, PL syntax, etc).
I don't have an opinion on bilingual ballots or not.
Not even for bilingual texts for medicine or not. I guess French or Russian or whatever texts on medicine are fine.
My comment was strictly for developer documentation -- where everything in programming is in english, and even basic syntax and terminology needs tons of english to grok anyway.
So English + development is more like a case of being an Egyptologist and not speaking ancient Egyptian -- they go with the profession.
That's covered by the use of "expected" I think (as expected != is).
That said, trying to read it in English even if they struggle will benefit them more (even as developers, but also professionally) than using some regional translation as a clutch.
I wouldn't recommend the same for literature or news of course, but in programming english is like part of the basic science.
Normally I'll read and write any programming related documentation in english, since it's easier to share, refer to common terms and concept, lookup online, etc, and every dev is expected to be able to read it anyway (else they'll have much worse troubles with error messages, tooling, PL syntax, etc).