this post was submitted on 20 Aug 2024
620 points (88.8% liked)

Showerthoughts

29632 readers
699 users here now

A "Showerthought" is a simple term used to describe the thoughts that pop into your head while you're doing everyday things like taking a shower, driving, or just daydreaming. The best ones are thoughts that many people can relate to and they find something funny or interesting in regular stuff.

Rules

  1. All posts must be showerthoughts
  2. The entire showerthought must be in the title
  3. Avoid politics (NEW RULE as of 5 Nov 2024, trying it out)
  4. Posts must be original/unique
  5. Adhere to Lemmy's Code of Conduct

founded 1 year ago
MODERATORS
 

It sounds way less offensive to those who decry the original terminology's problematic roots but still keeps its meaning intact.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 16 points 2 months ago (2 children)

We're using server and agent, but im also a proponent of "captain" and "crew"

[–] [email protected] 4 points 2 months ago

I mentally replaced cars with boats recently and it's been inducing nautical terminology everywhere I speak. Cap'n and Crew sounds great for this usage, it feels honest without the shock of great grandpa's heavyweight authoritarianism. I usually wind up stepping down to Spongebob or Pirates to filter out seriousness too, as long as the packet arrives and the replicas are jolly.

[–] [email protected] 1 points 2 months ago (2 children)

The thing is that master has a different connotation in IT than server does. Such as in master/slave pairs for fault tolerance.

[–] [email protected] 1 points 2 months ago

Yes, both of those may already be servers

[–] [email protected] 1 points 2 months ago (1 children)

Fair enough. Im in devops and the first thing I thought about was Jenkins, where "server" and "agent" fit quite well.

I dont think master/slave is that good of a naming scheme for fault tolerance either, since the "slave" doesnt do work so that the master doesnt have to, but it's rather an active/reserve kind of thing.

But I also admit that using different terms that fit best for every usecase would only cause more confusion than good.

[–] [email protected] 1 points 2 months ago

I agree that active/reserve is a better way of saying it, and that's the way I've always said it when working with these systems. Honestly I may have never heard master slave in actual use in 15 years of regularly describing such systems.