• dbx12@programming.dev
    link
    fedilink
    arrow-up
    21
    ·
    6 months ago

    Review is done before code gets into main, but that’s inefficient for most of the non-mission critical projects out there. A better approach is to optimistically merge most changes as soon as not-rocket-science allows it, and then later review the code in situ, in the main branch.

    Assuming you have a project with continuous delivery, that is an absolute foot gun. Optimistically merge the change and then realize in situ that you forgot the WHERE part of your SQL command (or analog statement of the query builder)? No fucking thanks.

    • xoggy@programming.dev
      link
      fedilink
      arrow-up
      2
      ·
      edit-2
      6 months ago

      A better approach is to optimistically merge most changes as soon as not-rocket-science allows it, and then later review the code in situ, in the main branch.

      I upvoted before reviewing the article in situ, then I had to go back and fix my upvote.