▲ 1514 ▼ Absolute legend (lemmy.today) submitted 2 years ago by CmdrKeen@lemmy.today to c/programmer_humor@programming.dev 115 comments fedilink hide all child comments
[–] victorz@lemmy.world 36 points 2 years ago (15 children) Why would they do that? Talk about generating mistrust. permalink fedilink source parent hideshow 15 child comments replies: [–] henfredemars@infosec.pub 29 points 2 years ago (10 children) It may not be malice. Incompetence. permalink fedilink source parent hideshow 10 child comments replies: [–] jaybone@lemmy.world 5 points 2 years ago (9 children) They are going to “accidentally” remove a fix? permalink fedilink source parent hideshow 9 child comments replies: [–] henfredemars@infosec.pub 16 points 2 years ago (8 children) 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. permalink fedilink source parent hideshow 8 child comments replies: [–] siipale@sopuli.xyz 1 point 2 years ago (7 children) Can you give an example how that would happen? permalink fedilink source parent hideshow 7 child comments replies: [–] henfredemars@infosec.pub 9 points 2 years ago (5 children) It’s pretty straightforward. Merge conflicts? No such thing! Just make my version the next version. permalink fedilink source parent hideshow 5 child comments replies: [–] dejected_warp_core@lemmy.world 2 points 2 years ago (4 children) 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. permalink fedilink source parent hideshow 4 child comments replies: [–] henfredemars@infosec.pub 2 points 2 years ago (3 children) 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. permalink fedilink source parent hideshow 3 child comments replies: [–] dejected_warp_core@lemmy.world 2 points 2 years ago (2 children) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] henfredemars@infosec.pub 2 points 2 years ago (1 child) I now work for a small business but in the interest of not getting bitten in the ass I don’t wish to give the name of my previous employer. It was a large defense contractor, but our values didn’t align so I moved on when I found another opportunity to put food on the table. I know that’s not a satisfying answer but I’m here for entertainment value and the opportunity cost might not be worth it. My main point was that even though they have the money they didn’t see the value in good software process. All the time! We would leave bugs unfixed even if the fix was trivially easy because management felt productive listing it as a cost savings. Software maintenance was seen as a necessary evil. permalink fedilink source parent hideshow 1 child comment replies: [–] dejected_warp_core@lemmy.world 2 points 2 years ago Software maintenance was seen as a necessary evil. The most important lesson I learned about the economics of software is that sourcecode is always accounted as a liability and not an asset. Accountants will never let you code your way into more value. Everything else you see stems from that truth. permalink fedilink source parent [–] entropicdrift@lemmy.sdf.org 1 point 2 years ago Force push to the master branch or release branch, for one permalink fedilink source parent [–] mryessir@lemmy.sdf.org 1 point 2 years ago (2 children) Rehire obv. permalink fedilink source parent hideshow 2 child comments replies: [–] victorz@lemmy.world 1 point 2 years ago (1 child) Good luck with that lol. Who would fall for that. permalink fedilink source parent hideshow 1 child comment replies: [–] mryessir@lemmy.sdf.org 1 point 2 years ago Corporate rated this strategy viable permalink fedilink source parent [–] Sidhean@lemmy.world 0 points 2 years ago I dunno, but it'd be funny permalink fedilink source parent
[–] henfredemars@infosec.pub 29 points 2 years ago (10 children) It may not be malice. Incompetence. permalink fedilink source parent hideshow 10 child comments replies: [–] jaybone@lemmy.world 5 points 2 years ago (9 children) They are going to “accidentally” remove a fix? permalink fedilink source parent hideshow 9 child comments replies: [–] henfredemars@infosec.pub 16 points 2 years ago (8 children) 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. permalink fedilink source parent hideshow 8 child comments replies: [–] siipale@sopuli.xyz 1 point 2 years ago (7 children) Can you give an example how that would happen? permalink fedilink source parent hideshow 7 child comments replies: [–] henfredemars@infosec.pub 9 points 2 years ago (5 children) It’s pretty straightforward. Merge conflicts? No such thing! Just make my version the next version. permalink fedilink source parent hideshow 5 child comments replies: [–] dejected_warp_core@lemmy.world 2 points 2 years ago (4 children) 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. permalink fedilink source parent hideshow 4 child comments replies: [–] henfredemars@infosec.pub 2 points 2 years ago (3 children) 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. permalink fedilink source parent hideshow 3 child comments replies: [–] dejected_warp_core@lemmy.world 2 points 2 years ago (2 children) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] henfredemars@infosec.pub 2 points 2 years ago (1 child) I now work for a small business but in the interest of not getting bitten in the ass I don’t wish to give the name of my previous employer. It was a large defense contractor, but our values didn’t align so I moved on when I found another opportunity to put food on the table. I know that’s not a satisfying answer but I’m here for entertainment value and the opportunity cost might not be worth it. My main point was that even though they have the money they didn’t see the value in good software process. All the time! We would leave bugs unfixed even if the fix was trivially easy because management felt productive listing it as a cost savings. Software maintenance was seen as a necessary evil. permalink fedilink source parent hideshow 1 child comment replies: [–] dejected_warp_core@lemmy.world 2 points 2 years ago Software maintenance was seen as a necessary evil. The most important lesson I learned about the economics of software is that sourcecode is always accounted as a liability and not an asset. Accountants will never let you code your way into more value. Everything else you see stems from that truth. permalink fedilink source parent [–] entropicdrift@lemmy.sdf.org 1 point 2 years ago Force push to the master branch or release branch, for one permalink fedilink source parent
[–] jaybone@lemmy.world 5 points 2 years ago (9 children) They are going to “accidentally” remove a fix? permalink fedilink source parent hideshow 9 child comments replies: [–] henfredemars@infosec.pub 16 points 2 years ago (8 children) 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. permalink fedilink source parent hideshow 8 child comments replies: [–] siipale@sopuli.xyz 1 point 2 years ago (7 children) Can you give an example how that would happen? permalink fedilink source parent hideshow 7 child comments replies: [–] henfredemars@infosec.pub 9 points 2 years ago (5 children) It’s pretty straightforward. Merge conflicts? No such thing! Just make my version the next version. permalink fedilink source parent hideshow 5 child comments replies: [–] dejected_warp_core@lemmy.world 2 points 2 years ago (4 children) 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. permalink fedilink source parent hideshow 4 child comments replies: [–] henfredemars@infosec.pub 2 points 2 years ago (3 children) 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. permalink fedilink source parent hideshow 3 child comments replies: [–] dejected_warp_core@lemmy.world 2 points 2 years ago (2 children) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] henfredemars@infosec.pub 2 points 2 years ago (1 child) I now work for a small business but in the interest of not getting bitten in the ass I don’t wish to give the name of my previous employer. It was a large defense contractor, but our values didn’t align so I moved on when I found another opportunity to put food on the table. I know that’s not a satisfying answer but I’m here for entertainment value and the opportunity cost might not be worth it. My main point was that even though they have the money they didn’t see the value in good software process. All the time! We would leave bugs unfixed even if the fix was trivially easy because management felt productive listing it as a cost savings. Software maintenance was seen as a necessary evil. permalink fedilink source parent hideshow 1 child comment replies: [–] dejected_warp_core@lemmy.world 2 points 2 years ago Software maintenance was seen as a necessary evil. The most important lesson I learned about the economics of software is that sourcecode is always accounted as a liability and not an asset. Accountants will never let you code your way into more value. Everything else you see stems from that truth. permalink fedilink source parent [–] entropicdrift@lemmy.sdf.org 1 point 2 years ago Force push to the master branch or release branch, for one permalink fedilink source parent
[–] henfredemars@infosec.pub 16 points 2 years ago (8 children) 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. permalink fedilink source parent hideshow 8 child comments replies: [–] siipale@sopuli.xyz 1 point 2 years ago (7 children) Can you give an example how that would happen? permalink fedilink source parent hideshow 7 child comments replies: [–] henfredemars@infosec.pub 9 points 2 years ago (5 children) It’s pretty straightforward. Merge conflicts? No such thing! Just make my version the next version. permalink fedilink source parent hideshow 5 child comments replies: [–] dejected_warp_core@lemmy.world 2 points 2 years ago (4 children) 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. permalink fedilink source parent hideshow 4 child comments replies: [–] henfredemars@infosec.pub 2 points 2 years ago (3 children) 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. permalink fedilink source parent hideshow 3 child comments replies: [–] dejected_warp_core@lemmy.world 2 points 2 years ago (2 children) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] henfredemars@infosec.pub 2 points 2 years ago (1 child) I now work for a small business but in the interest of not getting bitten in the ass I don’t wish to give the name of my previous employer. It was a large defense contractor, but our values didn’t align so I moved on when I found another opportunity to put food on the table. I know that’s not a satisfying answer but I’m here for entertainment value and the opportunity cost might not be worth it. My main point was that even though they have the money they didn’t see the value in good software process. All the time! We would leave bugs unfixed even if the fix was trivially easy because management felt productive listing it as a cost savings. Software maintenance was seen as a necessary evil. permalink fedilink source parent hideshow 1 child comment replies: [–] dejected_warp_core@lemmy.world 2 points 2 years ago Software maintenance was seen as a necessary evil. The most important lesson I learned about the economics of software is that sourcecode is always accounted as a liability and not an asset. Accountants will never let you code your way into more value. Everything else you see stems from that truth. permalink fedilink source parent [–] entropicdrift@lemmy.sdf.org 1 point 2 years ago Force push to the master branch or release branch, for one permalink fedilink source parent
[–] siipale@sopuli.xyz 1 point 2 years ago (7 children) Can you give an example how that would happen? permalink fedilink source parent hideshow 7 child comments replies: [–] henfredemars@infosec.pub 9 points 2 years ago (5 children) It’s pretty straightforward. Merge conflicts? No such thing! Just make my version the next version. permalink fedilink source parent hideshow 5 child comments replies: [–] dejected_warp_core@lemmy.world 2 points 2 years ago (4 children) 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. permalink fedilink source parent hideshow 4 child comments replies: [–] henfredemars@infosec.pub 2 points 2 years ago (3 children) 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. permalink fedilink source parent hideshow 3 child comments replies: [–] dejected_warp_core@lemmy.world 2 points 2 years ago (2 children) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] henfredemars@infosec.pub 2 points 2 years ago (1 child) I now work for a small business but in the interest of not getting bitten in the ass I don’t wish to give the name of my previous employer. It was a large defense contractor, but our values didn’t align so I moved on when I found another opportunity to put food on the table. I know that’s not a satisfying answer but I’m here for entertainment value and the opportunity cost might not be worth it. My main point was that even though they have the money they didn’t see the value in good software process. All the time! We would leave bugs unfixed even if the fix was trivially easy because management felt productive listing it as a cost savings. Software maintenance was seen as a necessary evil. permalink fedilink source parent hideshow 1 child comment replies: [–] dejected_warp_core@lemmy.world 2 points 2 years ago Software maintenance was seen as a necessary evil. The most important lesson I learned about the economics of software is that sourcecode is always accounted as a liability and not an asset. Accountants will never let you code your way into more value. Everything else you see stems from that truth. permalink fedilink source parent [–] entropicdrift@lemmy.sdf.org 1 point 2 years ago Force push to the master branch or release branch, for one permalink fedilink source parent
[–] henfredemars@infosec.pub 9 points 2 years ago (5 children) It’s pretty straightforward. Merge conflicts? No such thing! Just make my version the next version. permalink fedilink source parent hideshow 5 child comments replies: [–] dejected_warp_core@lemmy.world 2 points 2 years ago (4 children) 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. permalink fedilink source parent hideshow 4 child comments replies: [–] henfredemars@infosec.pub 2 points 2 years ago (3 children) 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. permalink fedilink source parent hideshow 3 child comments replies: [–] dejected_warp_core@lemmy.world 2 points 2 years ago (2 children) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] henfredemars@infosec.pub 2 points 2 years ago (1 child) I now work for a small business but in the interest of not getting bitten in the ass I don’t wish to give the name of my previous employer. It was a large defense contractor, but our values didn’t align so I moved on when I found another opportunity to put food on the table. I know that’s not a satisfying answer but I’m here for entertainment value and the opportunity cost might not be worth it. My main point was that even though they have the money they didn’t see the value in good software process. All the time! We would leave bugs unfixed even if the fix was trivially easy because management felt productive listing it as a cost savings. Software maintenance was seen as a necessary evil. permalink fedilink source parent hideshow 1 child comment replies: [–] dejected_warp_core@lemmy.world 2 points 2 years ago Software maintenance was seen as a necessary evil. The most important lesson I learned about the economics of software is that sourcecode is always accounted as a liability and not an asset. Accountants will never let you code your way into more value. Everything else you see stems from that truth. permalink fedilink source parent
[–] dejected_warp_core@lemmy.world 2 points 2 years ago (4 children) 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. permalink fedilink source parent hideshow 4 child comments replies: [–] henfredemars@infosec.pub 2 points 2 years ago (3 children) 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. permalink fedilink source parent hideshow 3 child comments replies: [–] dejected_warp_core@lemmy.world 2 points 2 years ago (2 children) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] henfredemars@infosec.pub 2 points 2 years ago (1 child) I now work for a small business but in the interest of not getting bitten in the ass I don’t wish to give the name of my previous employer. It was a large defense contractor, but our values didn’t align so I moved on when I found another opportunity to put food on the table. I know that’s not a satisfying answer but I’m here for entertainment value and the opportunity cost might not be worth it. My main point was that even though they have the money they didn’t see the value in good software process. All the time! We would leave bugs unfixed even if the fix was trivially easy because management felt productive listing it as a cost savings. Software maintenance was seen as a necessary evil. permalink fedilink source parent hideshow 1 child comment replies: [–] dejected_warp_core@lemmy.world 2 points 2 years ago Software maintenance was seen as a necessary evil. The most important lesson I learned about the economics of software is that sourcecode is always accounted as a liability and not an asset. Accountants will never let you code your way into more value. Everything else you see stems from that truth. permalink fedilink source parent
[–] henfredemars@infosec.pub 2 points 2 years ago (3 children) 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. permalink fedilink source parent hideshow 3 child comments replies: [–] dejected_warp_core@lemmy.world 2 points 2 years ago (2 children) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] henfredemars@infosec.pub 2 points 2 years ago (1 child) I now work for a small business but in the interest of not getting bitten in the ass I don’t wish to give the name of my previous employer. It was a large defense contractor, but our values didn’t align so I moved on when I found another opportunity to put food on the table. I know that’s not a satisfying answer but I’m here for entertainment value and the opportunity cost might not be worth it. My main point was that even though they have the money they didn’t see the value in good software process. All the time! We would leave bugs unfixed even if the fix was trivially easy because management felt productive listing it as a cost savings. Software maintenance was seen as a necessary evil. permalink fedilink source parent hideshow 1 child comment replies: [–] dejected_warp_core@lemmy.world 2 points 2 years ago Software maintenance was seen as a necessary evil. The most important lesson I learned about the economics of software is that sourcecode is always accounted as a liability and not an asset. Accountants will never let you code your way into more value. Everything else you see stems from that truth. permalink fedilink source parent
[–] dejected_warp_core@lemmy.world 2 points 2 years ago (2 children) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] henfredemars@infosec.pub 2 points 2 years ago (1 child) I now work for a small business but in the interest of not getting bitten in the ass I don’t wish to give the name of my previous employer. It was a large defense contractor, but our values didn’t align so I moved on when I found another opportunity to put food on the table. I know that’s not a satisfying answer but I’m here for entertainment value and the opportunity cost might not be worth it. My main point was that even though they have the money they didn’t see the value in good software process. All the time! We would leave bugs unfixed even if the fix was trivially easy because management felt productive listing it as a cost savings. Software maintenance was seen as a necessary evil. permalink fedilink source parent hideshow 1 child comment replies: [–] dejected_warp_core@lemmy.world 2 points 2 years ago Software maintenance was seen as a necessary evil. The most important lesson I learned about the economics of software is that sourcecode is always accounted as a liability and not an asset. Accountants will never let you code your way into more value. Everything else you see stems from that truth. permalink fedilink source parent
[–] henfredemars@infosec.pub 2 points 2 years ago (1 child) I now work for a small business but in the interest of not getting bitten in the ass I don’t wish to give the name of my previous employer. It was a large defense contractor, but our values didn’t align so I moved on when I found another opportunity to put food on the table. I know that’s not a satisfying answer but I’m here for entertainment value and the opportunity cost might not be worth it. My main point was that even though they have the money they didn’t see the value in good software process. All the time! We would leave bugs unfixed even if the fix was trivially easy because management felt productive listing it as a cost savings. Software maintenance was seen as a necessary evil. permalink fedilink source parent hideshow 1 child comment replies: [–] dejected_warp_core@lemmy.world 2 points 2 years ago Software maintenance was seen as a necessary evil. The most important lesson I learned about the economics of software is that sourcecode is always accounted as a liability and not an asset. Accountants will never let you code your way into more value. Everything else you see stems from that truth. permalink fedilink source parent
[–] dejected_warp_core@lemmy.world 2 points 2 years ago Software maintenance was seen as a necessary evil. The most important lesson I learned about the economics of software is that sourcecode is always accounted as a liability and not an asset. Accountants will never let you code your way into more value. Everything else you see stems from that truth. permalink fedilink source parent
[–] entropicdrift@lemmy.sdf.org 1 point 2 years ago Force push to the master branch or release branch, for one permalink fedilink source parent
[–] mryessir@lemmy.sdf.org 1 point 2 years ago (2 children) Rehire obv. permalink fedilink source parent hideshow 2 child comments replies: [–] victorz@lemmy.world 1 point 2 years ago (1 child) Good luck with that lol. Who would fall for that. permalink fedilink source parent hideshow 1 child comment replies: [–] mryessir@lemmy.sdf.org 1 point 2 years ago Corporate rated this strategy viable permalink fedilink source parent
[–] victorz@lemmy.world 1 point 2 years ago (1 child) Good luck with that lol. Who would fall for that. permalink fedilink source parent hideshow 1 child comment replies: [–] mryessir@lemmy.sdf.org 1 point 2 years ago Corporate rated this strategy viable permalink fedilink source parent
[–] mryessir@lemmy.sdf.org 1 point 2 years ago Corporate rated this strategy viable permalink fedilink source parent
[–] Sidhean@lemmy.world 0 points 2 years ago I dunno, but it'd be funny permalink fedilink source parent