Well yeah, but you rarely write programs about science and computer stuff. You write programs about some business/domain where English might not be The Language.
Don't your customers complain that you write the requirement documents in English instead of the local language?
A big advantage you have as a local developer over an Indian developer is that you speak the native language of your customer. It seems kinda silly to throw that kind of an advantage away.
Besides, you can't really apply the principles from Domain Driven Design if you translate everything to English. You would end up with one language in your code and another language to talk to your customers, instead of a single ubiquitous language. This becomes especially difficult when you have a complex domain with tricky business rules that requires frequent collaboration with domain experts.