Timeline for Logging without Code Bloat
Current License: CC BY-SA 3.0
17 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 30, 2014 at 0:05 | history | edited | rolfl | CC BY-SA 3.0 | typos |
| Mar 31, 2014 at 20:32 | vote | accept | Nick Williams | ||
| Mar 27, 2014 at 0:28 | answer | added | Justin | timeline score: 9 | |
| Mar 26, 2014 at 8:47 | comment | added | abuzittin gillifirca | I noticed UriAgassi italicized operations too, in my case it was because it's not clear who operations is. Requirements coming from COO or IT Operations have different goals, different solutions that address them and they might have different priorities. | |
| Mar 26, 2014 at 8:31 | comment | added | abuzittin gillifirca | What you want is not logging, operations actually either want an audit trail or event sourcing. Logs are not reliable: You logged "Something done on bar with id=...", but what if changes to dbContext never saved? | |
| Mar 25, 2014 at 7:59 | history | tweeted | twitter.com/#!/StackCodeReview/status/448368527624658944 | ||
| Mar 24, 2014 at 20:58 | answer | added | Sten Petrov | timeline score: 2 | |
| Mar 24, 2014 at 17:32 | answer | added | Peteris | timeline score: 1 | |
| Mar 24, 2014 at 16:06 | history | edited | Jesse C. Slicer | CC BY-SA 3.0 | corrected spellings |
| Mar 24, 2014 at 15:19 | history | edited | Nick Williams | CC BY-SA 3.0 | added 9 characters in body |
| Mar 24, 2014 at 15:05 | answer | added | Nzall | timeline score: 6 | |
| Mar 24, 2014 at 14:14 | answer | added | David Mulder | timeline score: 1 | |
| Mar 24, 2014 at 13:12 | history | edited | svick | CC BY-SA 3.0 | rm thanks |
| Mar 24, 2014 at 12:22 | answer | added | Uri Agassi | timeline score: 20 | |
| Mar 24, 2014 at 10:32 | history | migrated | from programmers.stackexchange.com (revisions) | ||
| Mar 24, 2014 at 10:00 | answer | added | Bill Michell | timeline score: 30 | |
| Mar 24, 2014 at 9:48 | history | asked | Nick Williams | CC BY-SA 3.0 |