That was the moment I realised most of the api calls I'd been making used the American spelling.
To expand on my proviso: if a codebase is written by and for British developers, I see little reason to use American English. For a serious international FOSS project though, American English makes the most sense.
It's costly to have a codebase undecided on proper English vs American English. If Alice writes 'initialize' and Bob writes 'initialise', it causes pain for everyone. This even applies to keywords and reserved identifiers. For instance, in Ruby, methods named 'initialize' get special treatment.
American English tends to dominate in tech, so if we have to make a choice, it's clear enough which one it should be.
Incidentally, Google [3], and apparently also Microsoft [4], agree with us.
> For comments I use British English, I wouldn't know how to write American grammar if I tried.
I think I could cope if the need arose (it hasn't for some time, for me). As you imply, the real value is in consistent spelling in the API, rather than in the comments.
[0] http://www.catb.org/~esr/faqs/hacker-howto.html#skills4
[1] https://blog.codinghorror.com/the-ugly-american-programmer/
[2] https://news.ycombinator.com/item?id=538473
[3] https://developers.google.com/style/spelling
[4] https://stackoverflow.com/questions/157807/gb-english-or-us-...
For comments I use British English, I wouldn't know how to write American grammar if I tried.