Timeline for Is it acceptable to capitalize class names and attributes when referencing my programming code in a message?
Current License: CC BY-SA 3.0
8 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jul 9, 2013 at 16:21 | comment | added | theblang |
@TrevorD Well, I am not really using programming terms. I am using class and attribute names that refer to actual items in their business system. For example, I added filing date to the deed record . For some reason I was feeling the urge to write I added Filing Date to the Deed record because filingDate and Deed are an attribute and class in my code. The message would be short so I don't think I would want to add a header section with definitions as suggested by some below.
|
|
Jun 17, 2013 at 23:12 | comment | added | TrevorD | In the light of your comment below "I am writing to the people contracting us that have no programming experience.", surely you should be avoiding the use of programming terminology and should be asking questions / writing documentation in English. You're the one they have paid to translate between English & programming languages. But if you really, really must use programming terms, then define/explain them at the beginning so that they understand what these strange-looking camelCase words mean. This is a common-sense question, not an English language question! | |
Jun 17, 2013 at 22:43 | answer | added | Heatsink | timeline score: 2 | |
Jun 17, 2013 at 22:11 | history | edited | theblang | CC BY-SA 3.0 |
changed to reflect that it is not documentation, which you would definitely not want to capitalize
|
Jun 17, 2013 at 21:22 | review | First posts | |||
Jun 17, 2013 at 22:00 | |||||
Jun 17, 2013 at 21:14 | answer | added | tchrist♦ | timeline score: 2 | |
Jun 17, 2013 at 21:10 | answer | added | Kaiser Octavius | timeline score: 3 | |
Jun 17, 2013 at 21:05 | history | asked | theblang | CC BY-SA 3.0 |