864
Rest in peace.... (europe.pub)
submitted 2 months ago by to c/programmer_humor@programming.dev
49 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] 4 points 2 months ago (4 children)

Code should ideally be going through tests before prod anyway. There should be no code changed from successful test to prod. Proofreading shouldn’t matter at that point. Just scheduling the actual deploy.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 4 points 2 months ago (3 children)

    I mostly mean proof what I've written prior to having someone else test. I often will comment out lines when trying different things so I just make sure I clean up what I've done. We have a few human checks as well as some automated checks between each stage of deployment for each environment.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 1 point 2 months ago (2 children)

    Yeah that’s what the MRs are supposed to be for. To catch those and proofread.

    There shouldn’t be any changes at all from the last test to going to production though. Even cleaning up comments.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 months ago (1 child)

    Correct. I'm just saying that I proof read my work, that I deploy things, and that I don't proof read my texts.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 2 points 2 months ago

    No I got that. I’m saying that by the time the prod deploy comes around, there’s no proofreading left to do anyway.

    Not proofreading texts should have zero bearing on being able to write and deploy software because it should be proofread several times before the actual prod deployment. Hell it very likely isn’t even the same person doing the deployment that wrote the code.

  • permalink
  • fedilink
  • source
  • parent