Code reviews are the glue of any effective software engineering team. A code review is the stage at which an engineer requests their changes to be ...
For further actions, you may consider blocking this person and/or reporting abuse
I am one of those people who go through all the code to be reviewed, disregarding of its amount.
One important thing about any code review is to handle criticism - keep it professional and your ego out of it on both sides of the review.
Open the mind for a new idea 😄
True
totally true .
Where elements can be done by the machine, do them, computer time is very cheap, compared to the engineer.
Linting, static analysis, unit testing, dynamic analysis (where possible), integration tests.
Anything that allows the reviewer(s) to focus on the details that cannot be covered by the machine analysis.
it's my daily job to review and merge all the PR. it's true very challenging if there's 1000 line of codes to review. 😅
How you will mange the review of 1000 lines of code is important.
i will go through which of not following the standard first, before commenting on functionalities wise.
Code review should be the less stressful part 😴
be an explorer
Bookmarked this for reading later
I often look at my teams PRs and don’t feel like I don’t have any feedback. Is that bad? Am I supposed to put comments in even if the code looks fine too me?