1499
Absolute legend
(lemmy.today)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 20 May 2024
1499 points (97.7% liked)
Programmer Humor
19572 readers
1623 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 1 year ago
MODERATORS
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.
Are there a lot of these kinds of problems?
Which Fortune 500 company do you work for?
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.
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.
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