39
Tips for Reviewing Code (lemmy.world)
submitted 2 weeks ago by to c/programming@programming.dev
24 comments fedilink hide all child comments
 

Hello all. I work on a small team and I’ve been tasked with taking on the bulk of code review for when my senior goes on leave. Although I’ve read a fair bit of code (man am I lucky I learned to code before AI “got good”) I can’t say I’ve done a lot of actual “review”. Does anyone have any tips? I feel responsible if anything breaks after I review it so of course I want to avoid that.

you are viewing a single comment's thread
view the rest of the comments
[–] 7 points 2 weeks ago

Guidelines, best practices... Every company and every developer team has their own way of doing things. Start from there. If nothing is written down, be the one to do that and make it roll.

The comments I've read here are great, take them in.

I would add to be very picky with very junior or sloppy code, don't let that shit pass. For senior stuff just gloss over and check for glaring issues.

  • permalink
  • fedilink
  • source
    •