Hacker News new | past | comments | ask | show | jobs | submit login

I wouldn't use fixed values myself, but when I've worked at places with 100k+ hosts using naming schemes with consistent abbreviations of the same lengths, with other fields describing consistent data is much better than fun names when you need to fix things quickly.

Different story for small networks, have fun all you want. With hundreds of thousands of hosts scattered all over the world, this isn't used.




I haven't said a word about fun names, I think you rather missed my point entirely.


I get it, you like full hostnames such as production-mail-server-and-occasional-nas-file-server.

I'm just pointing out the fact that billion dollar real world orgs use abbreviated hostnames more often than not, and they have good reasons to do so.


If you got it, you wouldn't be putting up a straw man of long server names like "production-mail-server-and-occasional-nas-file-server" so no, you really don't get it because you aren't listening.

You can have short server names that are easy to type AND still use actual words. Typing prd instead of prod is not saving you anything worth saving nor making server names easier to type or remember no matter how many there are.

While

    production-mail-server-and-occasional-nas-file-server
is an absurd name, it was your example so I assume part of the scheme in this big network, but you'd just have well crammed all the same info into...

    prod-mail-file
Without abbreviations and without losing the meaning.

> and they have good reasons to do so.

Yea, inertia.


The real world companies I've worked for in the past have good reason to use abbreviated host names, sorry this is so offensive, but that's...real life?




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: