Timeline for Naming a "do X if needed" method
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 6, 2021 at 17:00 | comment | added | Daniel Dror | similar question: stackoverflow.com/q/3160261/929164 | |
| Aug 21, 2012 at 19:25 | vote | accept | dbkk | ||
| Aug 21, 2012 at 19:25 | vote | accept | dbkk | ||
| Aug 21, 2012 at 19:25 | |||||
| Aug 21, 2012 at 18:44 | comment | added | Kevin McCormick | Just a point of recommendation, methods like this, while well intentioned, should be created with caution. Along the way they tend to get peppered into unrelated code under the guise of "just in case" or "adding a call to it in X() fixed a bug, but I'm not sure why". If you have the discipline to only call RefreshUserList() during LoginUser() and LogoutUser(), and not during, say GetUser() (where the list should be up-to-date already), then by all means the advice below applies. | |
| Aug 21, 2012 at 17:58 | answer | added | Mark Canlas | timeline score: 3 | |
| Aug 21, 2012 at 17:57 | answer | added | Mason Wheeler | timeline score: 36 | |
| Aug 21, 2012 at 17:56 | answer | added | Matt S | timeline score: 16 | |
| Aug 21, 2012 at 17:54 | history | asked | dbkk | CC BY-SA 3.0 |