Timeline for When should the programmer's spoken language be used during development?
Current License: CC BY-SA 3.0
16 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Jun 21, 2014 at 12:33 | history | suggested | Thomas Eding | CC BY-SA 3.0 |
Grammar fixes
|
| Jun 21, 2014 at 11:15 | review | Suggested edits | |||
| S Jun 21, 2014 at 12:33 | |||||
| Jun 20, 2014 at 12:39 | history | edited | shylynx | CC BY-SA 3.0 |
precision of decision rule
|
| Jun 20, 2014 at 12:24 | history | edited | shylynx | CC BY-SA 3.0 |
precision of words
|
| Jun 20, 2014 at 12:18 | comment | added | shylynx | @Phil Perry: No I don't mean users. Audience aren't users! Users are completely outside of consideration. With Audience are meant developers, reviewers, maintainers and persons that handle the code! | |
| Jun 19, 2014 at 18:56 | comment | added | Phil Perry | I think two different concepts are being conflated by @shylynx. One is the internal coding language for variable names and comments, and the other is the external presentation to users. Internationalization and national language support takes care of the second case, but for the first, unless you're absolutely sure than ONLY people speaking one language will ever maintain/expand/enhance this code, you should stick with English. You're more likely to find English-speaking people to do this work than any other language. | |
| S Jun 19, 2014 at 15:36 | history | suggested | Aaron Hall | CC BY-SA 3.0 |
Capitalization, word choice.
|
| Jun 19, 2014 at 15:27 | review | Suggested edits | |||
| S Jun 19, 2014 at 15:36 | |||||
| Jun 19, 2014 at 13:55 | history | edited | shylynx | CC BY-SA 3.0 |
precision of some terms
|
| Jun 19, 2014 at 13:52 | comment | added | shylynx | You are right, lets say "use the language the majority of audience speaks". And that is what I mean, its your decision what the main audience is: developers or maintainers! | |
| Jun 19, 2014 at 13:31 | comment | added | C.Champagne | I do not agree what you say about comments in the code: you are never 100% sure of the language your audience will speak. An application can be developped somewhere and maintained somewhere else. Furthermore I am so used to work in teams where there is at least someone who doesn't speak the same language than the rest of the team so English is a good arrangement. | |
| Jun 19, 2014 at 13:31 | comment | added | Daenyth |
What do you mean by corresponding pendants?
|
|
| Jun 19, 2014 at 13:18 | history | edited | shylynx | CC BY-SA 3.0 |
entry added
|
| Jun 19, 2014 at 13:13 | history | edited | shylynx | CC BY-SA 3.0 |
typos removed
|
| Jun 19, 2014 at 13:07 | history | edited | shylynx | CC BY-SA 3.0 |
recommendation for comments added
|
| Jun 19, 2014 at 12:54 | history | answered | shylynx | CC BY-SA 3.0 |