Timeline for Code review from domain non expert
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 26, 2023 at 4:40 | comment | added | Simon Geard | @BЈовић - that's why in my comment, I specified "smart but less experienced". The value comes from having a junior developer who's keen to learn from his more experienced peers, because they'll ask those questions. If they're not interested in learning, I'd agree that their reviews are all but useless. | |
| Sep 21, 2023 at 8:49 | comment | added | BЈовић | my experience is quite the opposite. people who are not experts tend to tell only typos and grammar mistakes. quite rarely i get useful feedback from them :( | |
| Sep 21, 2023 at 2:21 | comment | added | Simon Geard | Likewise... as an architect, I prefer to get my code reviewed by developers who are smart but less experienced, because if they don't understand the architect's work, they'll ask questions because they want to learn from the architect. And that works out great, because nine times out of ten, they learn something that makes them more useful to me... and the tenth time, they've found something that I got wrong. | |
| Sep 19, 2023 at 17:04 | history | answered | bta | CC BY-SA 4.0 |