@[email protected] to Programmer [email protected] • 4 months agoAbsolute legendlemmy.todaymessage-square99fedilinkarrow-up11.52K
arrow-up11.52KimageAbsolute legendlemmy.today@[email protected] to Programmer [email protected] • 4 months agomessage-square99fedilink
minus-square@[email protected]linkfedilink5•4 months agoThey are going to “accidentally” remove a fix?
minus-square@[email protected]linkfedilinkEnglish16•4 months 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-square@[email protected]linkfedilink1•4 months agoCan you give an example how that would happen?
minus-square@[email protected]linkfedilinkEnglish9•4 months agoIt’s pretty straightforward. Merge conflicts? No such thing! Just make my version the next version.
minus-square@[email protected]linkfedilink2•4 months 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-square@[email protected]linkfedilinkEnglish2•4 months 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-square@[email protected]linkfedilink2•4 months ago 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-square@[email protected]linkfedilink1•4 months agoForce push to the master branch or release branch, for one
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
I dunno, but it’d be funny
Rehire obv.
Good luck with that lol. Who would fall for that.
Corporate rated this strategy viable