phpc.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A server for PHP programmers & friends. Join us for discussions on the PHP programming language, frameworks, packages, tools, open source, tech, life, and more.

Administered by:

Server stats:

837
active users

For non English speaking coders...
Especially if working in

requires common language & terminology in code and business

Yet, I see many benefits of coding in English....
- code homogeneity between public front end and internal code
- easier to find subcontractors
- English kinda is _the_ standard
- devs are more used to it
- pear review
- "auditability" (For context, my company's lg is FR... but HQ is British)
- ...

What do you do ?

(Boosts appreciated)

@dgoosens this misses the right answer: mixed

There are technical termsy where English is the only choice ("get" for a getter is the trivial) but business terms might be local, as this is easy to map to business requirements and English terms may have a (slightly) different meaning. (Especially when legal requirements are involved)

In my past I did financial bilance analysis and after few iterations "getEigenkapitalrendite()" was the clear winner.

Dmitri Goosens :elephpant:

@johannes
Yes… you’re not first one to mention that and it definitely is the right approach in my opinion