I don't feel the analogy is entirely accurate. Imagine having to learn 5 "if" statements, or 10 ways to say "++". In a spoken conversation, you don't get to look up the API docs if you forgot something. However, most programmers are likely at least bilingual because most programming books are in English and many companies in non-English countries use English as a common language.
However, I do feel there's some similarities between constructing a possibly-correct sentence and seeing if it actually works, and constructing some possibly-correct code and seeing if it compiles.
> most programmers are likely at least bilingual because most programming books are in English and many companies in non-English countries use English as a common language.
Reading English is a smallish subset of fluency in English, i.e. being able to also speak, listen to, and write English. Technical specs often use simple written English, relying on example code. So I'm not sure if what non-English programmers do can be called "bilingualism".
However, I do feel there's some similarities between constructing a possibly-correct sentence and seeing if it actually works, and constructing some possibly-correct code and seeing if it compiles.