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.

  • kiku@feddit.org
    link
    fedilink
    arrow-up
    9
    ·
    6 days ago

    If you don’t understand someone’s code, be brave and leave a comment saying you don’t understand. If you can’t understand it, the next person who has to maintain it won’t either. It’s a strong indication that refactoring should be done.

    Also if something breaks, just remember that you can roll back.

    Good luck!