Timeline for How to clean up code that requires a lot of user informing code
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 8, 2021 at 18:34 | history | became hot network question | |||
| S Oct 8, 2021 at 12:13 | review | Reopen votes | |||
| Oct 8, 2021 at 12:18 | |||||
| S Oct 8, 2021 at 12:13 | history | reopened | Thomas Owens♦ | ||
| Oct 8, 2021 at 12:12 | history | closed | Thomas Owens♦ | Not suitable for this site | |
| Oct 8, 2021 at 12:00 | history | tweeted | twitter.com/StackSoftEng/status/1446445306808258562 | ||
| Oct 8, 2021 at 11:59 | comment | added | Jörg W Mittag | Have you considered following the traditional Unix approach to only tell the user about things that are going wrong? If a utility works as desired, there should be no output at all (unless of course the purpose of the utility is to output something). | |
| Oct 8, 2021 at 11:45 | vote | accept | Krowi | ||
| Oct 8, 2021 at 10:45 | answer | added | David Arno | timeline score: 5 | |
| Oct 8, 2021 at 10:29 | history | asked | Krowi | CC BY-SA 4.0 |