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

  • SkyNTP@lemmy.ca
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    10 months ago

    What does “stale code” even mean in this context?

    Does that mean it falls behind stable? Just merge stable into your branch; problem solved.

    Or is this just some coded language for “people aren’t adopting my ideas fast enough”. Stop bitching and get good.

  • will_a113@lemmy.ml
    link
    fedilink
    English
    arrow-up
    1
    ·
    10 months ago

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

  • sirdorius@programming.dev
    link
    fedilink
    arrow-up
    1
    ·
    10 months ago

    I really wish LinkedIn would add an anonymous cringe emoji. I would use it on like 90% of the content on that site.

  • simple@lemm.ee
    link
    fedilink
    arrow-up
    1
    ·
    10 months ago

    Having to go through the process of merging hurts morale and slows performance. Give everyone on your team the right to force push to master.

  • DefinitelyNotAPhone [he/him]@hexbear.net
    link
    fedilink
    English
    arrow-up
    0
    arrow-down
    1
    ·
    10 months ago

    Nothing improves morale like the on-call having to unfuck production for the third time that hour because mUh VeLoCiTy decided code review and testing in CI was too slow.

    Techbros are fucking cultists.