Move fast and break things.
Merge vulnerabilities.
Double the work.
Merge code without tests.
Anything, but don’t let code become stale.

  • vrkr@programming.dev
    1·
    11 months ago

    Something like that happened to me yesterday. I reviewed one PR, then some Important Guy came in and said:

    • it is nice you reviewed my work, but we need to push this to production right now.
    • just fix these things, I described you how. Just copy/paste these snippets
    • these are cosmetics, I don’t care
    • “cosmetics”, huh? Your shit may just crash
    • gfy and push this to production right now
    • well, ok

    Of course, lack of these “cosmetics” caused crash in production. It’s my fault of course.

  • bleistift2@feddit.deEnglish
    0·
    11 months ago

    My old boss (at a sturtup with some ten ppl) loved to do this. When you’re done with your work, merge to master. Boss-man would then revert the commits if he didn’t like the result. Since the branches all were merged, no-one knew what was actually in prod. Fun times.

  • gatelike@feddit.deEnglish
    0·
    11 months ago

    this made my heart rate go up a little bit in a way that doesn’t feel good

  • will_a113@lemmy.mlEnglish
    0·
    11 months ago

    Having a hard time determining whether this is sarcasm or not. Then I see the phrase “JavaScript Engineer” and become doubly confused.