Post History
I currently spend a good deal of time over at Code Review and I would love to improve the quality of the reviews I write. Can you give me any insight into the structure or approach you use when wri...
#3: Attribution notice added
by
System
·
2019-12-08T11:01:50Z (over 4 years ago)
Source: https://writers.stackexchange.com/q/42639 License name: CC BY-SA 3.0 License URL: https://creativecommons.org/licenses/by-sa/3.0/
#2: Initial revision
by
AGirlHasNoName
·
2019-12-08T11:01:50Z (over 4 years ago)
I currently spend a good deal of time over at Code Review and I would love to improve the quality of the reviews I write. Can you give me any insight into the structure or approach you use when writing a Code Review (be it on Stack Exchange or otherwise.) While I do understand that professional code reviews aren't going to look exactly the same as those on Stack Exchange, I would appreciate a perspective into how you would structure one professionally. Where do you start? Architecture and design? Algorithm? Seriousness of flaw? Do you structure it in any meaningful way? Do you weigh in on controversial "best practices" topics that may not be overtly wrong in this use case? Do you provide links to articles or Stack Overflow Questions and Answers to support your review? How far do you go to solve the problem? What have I missed?
#1: Imported from external source
by
System
·
2019-02-26T03:46:20Z (about 5 years ago)
Original score: 8