N3Cr0@lemmy.world to Programmer Humor@lemmy.ml · 2 months agoIt happens each time!lemmy.worldimagemessage-square15fedilinkarrow-up114arrow-down11
arrow-up113arrow-down1imageIt happens each time!lemmy.worldN3Cr0@lemmy.world to Programmer Humor@lemmy.ml · 2 months agomessage-square15fedilink
minus-squareCyborganism@lemmy.calinkfedilinkarrow-up1·2 months agoYou need to merge more often. Rebase. That’s where the real trauma is.
minus-squareurquell@lemm.eelinkfedilinkarrow-up1·2 months agoAnd the branch should be alive a shorter period
minus-squarezalgotext@sh.itjust.workslinkfedilinkarrow-up0·2 months agoNeither rebasing nor merging should cause trauma if everyone on the team takes a day or two to understand git
minus-squareArtyom@lemm.eelinkfedilinkarrow-up0·2 months agoYou and I have very different opinions on what is a reasonable expectation for our respective teams.
minus-squarezalgotext@sh.itjust.workslinkfedilinkarrow-up0·2 months agoYou think it’s unreasonable for a software developer to take one to two days to learn a tool that’s basically ubiquitous in their field?
minus-squareArtyom@lemm.eelinkfedilinkarrow-up1·2 months agoNo, I think it’s a perfectly reasonable thing to do, my coworkers on the other hand…
You need to merge more often.
Rebase. That’s where the real trauma is.
And the branch should be alive a shorter period
Neither rebasing nor merging should cause trauma if everyone on the team takes a day or two to understand git
You and I have very different opinions on what is a reasonable expectation for our respective teams.
You think it’s unreasonable for a software developer to take one to two days to learn a tool that’s basically ubiquitous in their field?
No, I think it’s a perfectly reasonable thing to do, my coworkers on the other hand…