Timeline for Is using uncommon words as descriptive variable names acceptable?
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 20, 2016 at 10:25 | audit | Suggested edits | |||
| Nov 20, 2016 at 11:50 | |||||
| Oct 26, 2016 at 20:57 | comment | added | Doc Brown | "stimulus" looks fine to me, but if you do not like it, you could also write "trigger", as long as you are not working in a database context where the latter could be intermixed with database triggers. | |
| Oct 26, 2016 at 20:24 | review | Close votes | |||
| Oct 31, 2016 at 3:01 | |||||
| Oct 26, 2016 at 20:15 | comment | added | Patrick Hughes | Extremely common word. In any case, if the word concisely means what it means then it's up to the reader to look it up and add it to their working vocabulary instead of using five words in its place to mean the same thing. Way better than decoce_next_state(thingThatCausesOtherThingToHappen) | |
| Oct 26, 2016 at 18:57 | vote | accept | skrrgwasme | ||
| Oct 26, 2016 at 18:24 | answer | added | Robert Harvey | timeline score: 10 | |
| Oct 26, 2016 at 18:12 | comment | added | MetalMikester | @Servy I don't know. It seems clear to me, but I'm having a weird day. | |
| Oct 26, 2016 at 18:09 | comment | added | Servy | @MetalMikester It's not a work I'd consider uncommon in general; I haven't ever seen it used in this context to describe something like this (not that I have a particular problem with it, just saying the OP's concerns may at least be worth considering). | |
| Oct 26, 2016 at 18:07 | comment | added | MetalMikester | "stimulus" is not a word I find uncommon. | |
| Oct 26, 2016 at 18:04 | comment | added | Becuzz | If it describes the purpose well and everyone will / should be able to understand it, what are you worried about? The name is for you and other programmers to read. Pick whatever best conveys the purpose. | |
| Oct 26, 2016 at 18:00 | history | asked | skrrgwasme | CC BY-SA 3.0 |