CmdrKeen@lemmy.today to Programmer Humor@programming.dev · 1年前Absolute legendlemmy.todayimagemessage-square116fedilinkarrow-up11.55Karrow-down136
arrow-up11.51Karrow-down1imageAbsolute legendlemmy.todayCmdrKeen@lemmy.today to Programmer Humor@programming.dev · 1年前message-square116fedilink
minus-squareVictor@lemmy.worldlinkfedilinkarrow-up37arrow-down1·1年前Why would they do that? Talk about generating mistrust.
minus-squarehenfredemars@infosec.publinkfedilinkEnglisharrow-up31arrow-down2·1年前It may not be malice. Incompetence.
minus-squarejaybone@lemmy.worldlinkfedilinkarrow-up5·1年前They are going to “accidentally” remove a fix?
minus-squarehenfredemars@infosec.publinkfedilinkEnglisharrow-up16·1年前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.
minus-squaresiipale@sopuli.xyzlinkfedilinkarrow-up1·1年前Can you give an example how that would happen?
minus-squarehenfredemars@infosec.publinkfedilinkEnglisharrow-up9·1年前It’s pretty straightforward. Merge conflicts? No such thing! Just make my version the next version.
minus-squaredejected_warp_core@lemmy.worldlinkfedilinkarrow-up2·1年前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.
minus-squarehenfredemars@infosec.publinkfedilinkEnglisharrow-up2·1年前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.
minus-squaredejected_warp_core@lemmy.worldlinkfedilinkarrow-up2·1年前 A times B times C equals X. If X is more than the cost of a failure or security breach, we don’t fix the software. Are there a lot of these kinds of problems? You wouldn’t believe. Which Fortune 500 company do you work for? A major one.
minus-squareentropicdrift@lemmy.sdf.orglinkfedilinkarrow-up1·1年前Force push to the master branch or release branch, for one
minus-squareVictor@lemmy.worldlinkfedilinkarrow-up1·1年前Good luck with that lol. Who would fall for that.
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.
Are there a lot of these kinds of problems?
Which Fortune 500 company do you work for?
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