Timeline for Code review from domain non expert
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 21, 2023 at 11:48 | comment | added | user213769 | @MartinBa fully agree. An in-depth review is better than cursory review, but a cursory review is still a lot better than no review, and more eyes on code are always better. Some people say "but why do I need a review from someone who doesn't understand the problem?" The answer is: "to see why the problem is hard to understand". Even responses about required updates/additions to in-code documentation or comments are valuable, regardless of what some people think. Non-expert reviewers are expert at finding hard-to-understand or badly-documented-and-completely-opaque stuff. | |
| Sep 19, 2023 at 13:23 | comment | added | Martin Ba | This. Kid or Senior: You can always find bugs or mishaps in some code, even if you have no clue what it's doing on a domain level. Might not be ideal, but better than nothin. | |
| Sep 19, 2023 at 6:51 | history | answered | gnasher729 | CC BY-SA 4.0 |