[{"data":1,"prerenderedAt":80},["ShallowReactive",2],{"entry-\u002Fblog\u002Fwhat-review-taught-me-vi":3},{"entry":4,"writtenIn":79,"onlyIn":79},{"id":5,"title":6,"body":7,"date":65,"description":66,"extension":67,"meta":68,"navigation":69,"path":70,"role":71,"seo":72,"stack":73,"stem":74,"tags":75,"year":71,"__hash__":78},"content_en\u002Fblog\u002Fwhat-review-taught-me.md","What review taught me",{"type":8,"value":9,"toc":58},"minimark",[10,14,19,22,25,29,36,42,48,52,55],[11,12,13],"p",{},"I expected code review to make me better at spotting bugs in other people's work. It did, a little. What it actually changed was how I open a pull request.",[15,16,18],"h2",{"id":17},"reading-is-slower-than-writing","Reading is slower than writing",[11,20,21],{},"The author has the whole change loaded in their head. The reviewer has a diff, in file-alphabetical order, with no idea which part is the point.",[11,23,24],{},"That asymmetry is the entire problem, and almost every review frustration traces back to it. A reviewer who cannot find the point will either approve without reading or ask questions the author considers obvious. Both outcomes are the author's to prevent.",[15,26,28],{"id":27},"three-habits-that-came-out-of-it","Three habits that came out of it",[11,30,31,35],{},[32,33,34],"strong",{},"Separate the mechanical commit from the thinking commit."," A rename touching forty files and a logic change touching one should never arrive together. Reviewed separately, both are quick; reviewed together, the logic change is invisible.",[11,37,38,41],{},[32,39,40],{},"Say what you decided against."," \"I did not use a computed here because the value is read once during setup\" prevents the most common review comment before it is written. It costs one line.",[11,43,44,47],{},[32,45,46],{},"Point at the risky part."," Every change has one. Naming it is not an admission of weakness — it is directing the limited attention the reviewer has toward the place where it pays.",[15,49,51],{"id":50},"the-uncomfortable-part","The uncomfortable part",[11,53,54],{},"Most review comments I received were things I already knew and had skipped. Not knowledge gaps — attention gaps, at the end of a task when it felt done.",[11,56,57],{},"That is a harder problem than not knowing something, because you cannot read your way out of it. The only fix I have found is mechanical: read the diff yourself, in the review interface, before assigning anyone. Half the comments never get written.",{"title":59,"searchDepth":60,"depth":60,"links":61},"",2,[62,63,64],{"id":17,"depth":60,"text":18},{"id":27,"depth":60,"text":28},{"id":50,"depth":60,"text":51},"2026-03-09","Two years of reading other people's diffs, and the habit it changed most was how I write my own.","md",{},true,"\u002Fblog\u002Fwhat-review-taught-me",null,{"title":6,"description":66},[],"blog\u002Fwhat-review-taught-me",[76,77],"review","process","1TKANv2FoS2u9-WjFuhdsWOX7k8q2IOPrDwSSQn5uQ0","en",1788956392665]