this post was submitted on 11 Feb 2025
967 points (96.5% liked)

Programmer Humor

25282 readers
659 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

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] Maggoty@lemmy.world 1 points 5 months ago (12 children)

But why even? There's no risk to changing it and some risk to keeping it. That's the reason for the push to change it. Keeping something just because it's tradition isn't a good idea outside ceremonies.

[–] weker01@sh.itjust.works 10 points 5 months ago* (last edited 5 months ago) (3 children)

There is definitely a risk in changing it. Many automation systems that assume there is a master branch needed to be changed. Something that's trivial yes but changing a perfectly running system is always a potential risk.

Also stuff like tutorials and documentation become outdated.

[–] Maggoty@lemmy.world -1 points 5 months ago (2 children)

If they can't change what's essentially a variable name without issues then should they be doing the job?

[–] MadhuGururajan@programming.dev 2 points 5 months ago

pray tell me how would you change the name in every script of an automation system that refers to master? Remember, you have to justify the time and cost to your manager or director!

load more comments (1 replies)
load more comments (1 replies)
load more comments (9 replies)