Live data from Hacker News

What's the story behind the names of Cloudflare's name servers? (2013)

blog.cloudflare.com

51–58 of 58 posts

Re: What's the story behind the names of Cloudflare's name servers? (2013)

#51
post #50
post #45

Earlier quoted context omitted.

Sure, not using a naming scheme and not hiring the artist would have unlocked the potential to make their software soooo much more robust…

It's not the single act, but the compound effect of millions of such acts across the entire industry.

Yeah? Well, you know, that's just like uh, your opinion, man.

Re: What's the story behind the names of Cloudflare's name servers? (2013)

#52
post #2

"Naming strategies for servers" seems like a big enough niche for there to exist a compendium somewhere already, but I couldn't find a good one.

The interesting taxonomy may be less about the source of the names and more about what properties they have

Re: What's the story behind the names of Cloudflare's name servers? (2013)

#53
post #51
post #50

Earlier quoted context omitted.

It's not the single act, but the compound effect of millions of such acts across the entire industry.

Yeah? Well, you know, that's just like uh, your opinion, man.

of course it is, never claimed it to be universal truth or something

Re: What's the story behind the names of Cloudflare's name servers? (2013)

#54
post #30

Earlier quoted context omitted.

Exactly, they weren't proactive. Wasting their time on useless fanfiction.

Yeah, I'm sure they've spent a significant time of their whole engineering department in the 13 years since the blog post on this!

The only useful thing they provide is DDOS protection and free analytics. For some reason the whole world is brainwashed into thinking we need all of these horrendous cloud providers. Hetzner is thankfully taking up the market. You need a server and that's it + some ddos protection.

Re: What's the story behind the names of Cloudflare's name servers? (2013)

#55

Just make it a uuid or some other kind of random a-z0-9 string to avoid all this whimsy and nuisance?

Yeah, very comfortable to use in a conversation.

> Yeah if I'm not mistaken the ticketing service is deployed on t56kl-293d1-5gqp7, do you think we should move it to iwi49-oaqq0-492fa?

Re: What's the story behind the names of Cloudflare's name servers? (2013)

#56
post #21

There are 2 hard problems in computer science: naming things and cache invalidation. Cloudflare writes about how it deals with the first one.

3 hard things: you missed counting things.

The joke only works if it's still two things.

Re: What's the story behind the names of Cloudflare's name servers? (2013)

#57
post #49
post #48

Earlier quoted context omitted.

The only way to properly realize human potential is to have no fun when doing your work? Are you really sure you want to live in a world like that?

There are different grades of "fun". You can do silly things at work, name your servers bob and lola, while still serve the functionality and needs of your customers. But hiring an artist to draw the server as ninjas because "they protect our customers"? What kind of value does that bring? And then you write a blog post about it? Seriously? Knowing when the fun needs to stop is a way to create valuable things in soci…

Have fun on your hill. Or not, if that's what you prefer.

Re: What's the story behind the names of Cloudflare's name servers? (2013)

#58
post #6

This is so cringe. I feel like software engineers are just overgrown toddlers stuck in kindergarten: "We named our servers with boy and girls names and hired an artist to draw their personalities as ninjas!!@!111". I mean, whats wrong with a plain old 4 character hash or whatever?

Common names are much easier for people to copy over and check. As opposed to a random jumble of numbers and letters.

Common names also seem retypeable, which is usually a bad idea because it is error prone, especially in certain fonts. Random jumbles make retyping untenable, so copy-paste is used, which can't make the same mistakes, but is still vulnerable to operator error with incomplete copies.
Post reply on HN