@[email protected] to Programmer [email protected] • 1 year agoAbsolute legendlemmy.todayimagemessage-square114fedilinkarrow-up11.52K
arrow-up11.52KimageAbsolute legendlemmy.today@[email protected] to Programmer [email protected] • 1 year agomessage-square114fedilink
minus-square@[email protected]linkfedilinkEnglish16•1 year 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•1 year agoForce push to the master branch or release branch, for one
minus-square@[email protected]linkfedilinkEnglish9•1 year agoIt’s pretty straightforward. Merge conflicts? No such thing! Just make my version the next version.
minus-square@[email protected]linkfedilink2•1 year 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•1 year 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•1 year 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.
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?
Force push to the master branch or release branch, for one
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?
Rehire obv.
Good luck with that lol. Who would fall for that.
Corporate rated this strategy viable
I dunno, but it’d be funny