11–20 of 38 posts
It's a double-edged sword as it can yield more correct code but also spend time in things that a formatter/linter would do.
Or implement requirements very literally without trying to second-guess them, or ask for clarification.
not sure about specifics in training but I had quite a lot of fun reading regular c++ code with variables in english only to scroll and find pages of comments in foreign language like russian or japanese... another fun with languages happens when coders for whatever reason insist on naming their variables using fusion of english and other language, such as "HornyWidget" (horny means upper in my language)
I interviewed at a Dutch company that had offices in Paris and the French programmers insisted in using French for all identifiers. Effectively it was job security for them.
Having worked at companies in both languages I didn't notice much difference in style. One thing that was pointed out to me is that trends and practices (TTD, agile etc.) take longer to reach the francosphere and that French companies are always X years behind their Silicon Valley contemporaries.
I first noticed a difference in national styles when I contributed a patch to fastjson, a JSON parser in Java from Alibaba. Take a look around the repo; it'll look odd to a western programmer. There is a lot of duplication. And the tests don't have names, they are numbered. https://github.com/alibaba/fastjson/blob/master/src/test/jav... This was several years ago. I did end up choosing it since it really was the fast…
I think this is the reason for that duplication and numbering
not sure about specifics in training but I had quite a lot of fun reading regular c++ code with variables in english only to scroll and find pages of comments in foreign language like russian or japanese... another fun with languages happens when coders for whatever reason insist on naming their variables using fusion of english and other language, such as "HornyWidget" (horny means upper in my language)
I interviewed at a Dutch company that had offices in Paris and the French programmers insisted in using French for all identifiers. Effectively it was job security for them.
I have seen some people apply similar techniques to code (eg identify authorship of malware) and I assume what you're asking would be a pretty simple variation of that.
I think California developers tend to be more forward-thinking, and embrace a “move fast and break things” style. Whereas East Coast devs tend to be more academic, structured and top-down.
Speculatively, I’d attribute this to the lack of non compete enforceability in California. Innovation tends to diffuse a lot faster, and that’s rewarded more of a forward-thinking culture. Then again, if there was a piece of code that could kill me if it fails, I’d go with an engineer in Boston before one from Palo Alto.
He said that even to this day, programmers in Romania still have a deep emphasis on book learning and an intolerance for bugs or mistakes.
IMO the bigger divide is between West Coast and East Coast programming styles. I think California developers tend to be more forward-thinking, and embrace a “move fast and break things” style. Whereas East Coast devs tend to be more academic, structured and top-down. Speculatively, I’d attribute this to the lack of non compete enforceability in California. Innovation tends to diffuse a lot faster, and that’s rewarded…
I don't know if it is common and not just a local sampling bias, but I've noticed my Indian colleagues (in the UK) are more often Java programmers. Perhaps java, and thus OOP, is more popular in India?