CmdrKeen@lemmy.today to Programmer Humor@programming.dev · 2 years agoAbsolute legendlemmy.todayexternal-linkmessage-square116linkfedilinkarrow-up11.55Karrow-down137
arrow-up11.51Karrow-down1external-linkAbsolute legendlemmy.todayCmdrKeen@lemmy.today to Programmer Humor@programming.dev · 2 years agomessage-square116linkfedilink
minus-squarehsdkfr734r@feddit.nllinkfedilinkarrow-up95arrow-down5·2 years agoLet the patch be part of the code for one or two minor releases. Then revert the changes of the patch.
minus-squareVictor@lemmy.worldlinkfedilinkarrow-up37arrow-down1·2 years agoWhy would they do that? Talk about generating mistrust.
minus-squarehenfredemars@infosec.publinkfedilinkEnglisharrow-up31arrow-down2·2 years agoIt may not be malice. Incompetence.
minus-squarejaybone@lemmy.worldlinkfedilinkarrow-up5·2 years agoThey are going to “accidentally” remove a fix?
minus-squarehenfredemars@infosec.publinkfedilinkEnglisharrow-up16·2 years agoBy not understanding how version control works. I’ve worked at places that had a surprising number of developers who would just merge things in ways that drop code from other developers.
minus-squaresiipale@sopuli.xyzlinkfedilinkarrow-up1·2 years agoCan you give an example how that would happen?
minus-squarehenfredemars@infosec.publinkfedilinkEnglisharrow-up9·2 years agoIt’s pretty straightforward. Merge conflicts? No such thing! Just make my version the next version.
minus-squaredejected_warp_core@lemmy.worldlinkfedilinkarrow-up2·2 years agoAlso that’s likely a team that doesn’t use a branching workflow, has poor review on merges, and/or using Git like it’s SVN.
minus-squarehenfredemars@infosec.publinkfedilinkEnglisharrow-up2·2 years agoHow optimistic. At my last workplace I got us to finally stop using zip files for version control. This was at a fortune 500 company. The utility of software is so great that even terrible processes are still functional to some degree.
minus-squareentropicdrift@lemmy.sdf.orglinkfedilinkarrow-up1·2 years agoForce push to the master branch or release branch, for one
minus-squareVictor@lemmy.worldlinkfedilinkarrow-up1·2 years agoGood luck with that lol. Who would fall for that.
minus-squaremryessir@lemmy.sdf.orglinkfedilinkarrow-up1·2 years agoCorporate rated this strategy viable
minus-squareSidhean@lemmy.worldlinkfedilinkarrow-up1arrow-down1·2 years agoI dunno, but it’d be funny
Let the patch be part of the code for one or two minor releases. Then revert the changes of the patch.
Why would they do that? Talk about generating mistrust.
It may not be malice. Incompetence.
They are going to “accidentally” remove a fix?
By not understanding how version control works. I’ve worked at places that had a surprising number of developers who would just merge things in ways that drop code from other developers.
Can you give an example how that would happen?
It’s pretty straightforward. Merge conflicts? No such thing! Just make my version the next version.
Also that’s likely a team that doesn’t use a branching workflow, has poor review on merges, and/or using Git like it’s SVN.
How optimistic. At my last workplace I got us to finally stop using zip files for version control. This was at a fortune 500 company.
The utility of software is so great that even terrible processes are still functional to some degree.
Force push to the master branch or release branch, for one
Rehire obv.
Good luck with that lol. Who would fall for that.
Corporate rated this strategy viable
I dunno, but it’d be funny
Calm down, Satan