Timeline for How to find positive things in a code review?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 18, 2016 at 16:07 | comment | added | user26452 | @AaronHall If the OP can find something positive to say about code written by other professional programmers, then by all means he or she should. However, if there is not, then there's no point in trying to make something up. Instead, the OP should focus on developer effort and learning, not the code itself. | |
| Oct 18, 2016 at 14:25 | comment | added | gnasher729 | @AaronHall: "Your code can serve as a good example how not to write code". Is that positive enough? | |
| Oct 17, 2016 at 22:24 | comment | added | Aaron Hall | "don't worry about giving good feedback if there's nothing good to measure" I find it hard to believe that he couldn't find at least something positive to say about code written by other professional programmers while still raising the bar on expectations for everyone's code. This doesn't answer the question - it's simply a contradiction. | |
| Oct 17, 2016 at 20:42 | history | answered | user26452 | CC BY-SA 3.0 |