3 ms·
+1 to this. I've developed the habit of reviewing my PRs before publishing them. When you assume the role of a reviewer, you end up catching a lot of little (an
by ayberk 6y ago
+1 to this. I've developed the habit of reviewing my PRs before publishing them. When you assume the role of a reviewer, you end up catching a lot of little (and sometimes big!) stuff, reducing the total turnaround time.
- tudorpavel 6y ago+1 to self code reviews, I almost always find stuff I've missed or could have done better.
- kyleashipley 6y agoI often comment on my own PRs to explain alternatives or tradeoffs I considered. These aren't necessarily worth capturing in permanent documentation or TODOs, but can share knowledge or build confidence that I've considered various angles that might come up in a review. I'll also call out places where I'm not happy with the implementation, looking for feedback, etc.