Timeline for Approach to designing maintainable, yet informative, user notification messages
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 16, 2019 at 3:01 | history | tweeted | twitter.com/StackSoftEng/status/1117986448811134976 | ||
| Apr 8, 2019 at 7:53 | comment | added | ACEG | @DDrmmr Like I mentioned in an answer below, I am in a privileged position, in that I can pretty much "write my own requirements", as long as the software does what it's supposed to do. I want to design it "the right way" more for myself, than because it is required by the users, who are my co-workers and for whom this software is just a small helping part of their daily work. | |
| Apr 8, 2019 at 7:46 | vote | accept | ACEG | ||
| Apr 8, 2019 at 7:41 | comment | added | ACEG | @gnasher729 Do you also have something constructive to add, besides fake outrage? Please read the post -- I said explicitly that these were trivial, made up examples to illustrate my point. | |
| Apr 7, 2019 at 10:03 | comment | added | gnasher729 | You are seriously suggesting to show an end user a message “entity created successfully”? | |
| Apr 6, 2019 at 13:44 | comment | added | D Drmmr | How to convey notifications/errors to the user is part of the requirements, not the software design. Therefore, it should be approached from the user's point of view. The use of past tense in your examples reveals you are doing it wrong. | |
| Apr 5, 2019 at 21:52 | answer | added | John Wu | timeline score: -1 | |
| Apr 4, 2019 at 16:50 | answer | added | Laiv | timeline score: 1 | |
| Apr 4, 2019 at 11:25 | answer | added | Hans-Martin Mosner | timeline score: 4 | |
| Apr 4, 2019 at 10:40 | review | Close votes | |||
| Apr 16, 2019 at 3:10 | |||||
| Apr 4, 2019 at 10:22 | history | asked | ACEG | CC BY-SA 4.0 |