Timeline for How to design AI to understand its selling decisions?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 27, 2015 at 12:31 | comment | added | jhocking | I voted this answer up because I do like this approach, but no commenting every single line isn't the be-all-end-all of explanations. While those comments are appreciated, they still require that you read and grok the entire code listing in order to understand what it's doing, and that can be tl;dr with no introductory overview. It doesn't have to be long, just one or two sentences of "this approach does so and so. here's a code example:" | |
| Apr 27, 2015 at 11:43 | comment | added | Philipp | @Jon instead of improving your answer I decided to write my own. | |
| Apr 27, 2015 at 10:51 | comment | added | Alex | @Jon I would argue that pointing out how something can be improved is useful. | |
| Apr 27, 2015 at 8:50 | comment | added | Jon | +1 for "this comment adds something useful to the post" - No it didn't. It didn't add anything. It only pointed out that something needs to be added. If commenting every. single. line. of. code. isn't enough, feel free to click 'edit'. | |
| Apr 27, 2015 at 8:21 | comment | added | Philipp | This answer would benefit from a more theoretical explanation of the concepts behind this code, how it works, why it works, and what the strengths and weaknesses of this method are. | |
| Apr 27, 2015 at 6:50 | history | edited | Jon | CC BY-SA 3.0 | added 424 characters in body |
| Apr 27, 2015 at 6:42 | history | answered | Jon | CC BY-SA 3.0 |