Every machine in my home stack is named after a Pokemon.
Theres hundreds of options, each pretty unique, and fun.
You also get some sense of scale, in that stronger machines can correlate to stronger pokes.<p>Beefy desktop with a strong GPU? Name it after a legendary.<p>RPI? One of the thousand little electric guys. Rotom, voltorb, .....<p>That daily driver laptop that never leaves your side? I usually pick a starter evo or eeveeloution<p>Cloud server? Pick a flying type.<p>It like having a theme to my whole infrastructure. Even my DuckDDNS is named after porygon, the cyber duck.
my first tech job was doing datacenter monkeywork and phone support for a small-town ISP. a lot of our older machines predated the "function-number" naming scheme (db01.foobar.net, web03.foobar.net etc) and instead were named after various Middle Earth locales. edge routers took regional names, firewalls usually took mountain names, web/file servers were named after big structures/cities etc. took me forever to learn (since i'd only read the books once at that point) but i've carried it with me for personal machine/local network naming ever since.<p>i like descriptive cattle names for machines i support professionally but home stuff gets to stay fun :)
> Don't use antagonistic or otherwise embarrassing names.<p><pre><code> Words like "moron" or "twit" are good names if no one else is
going to see them. But if you ever give someone a demo on your
machine, you may find that they are distracted by seeing a
nasty word on your screen. (Maybe their spouse called them
that this morning.) Why bother taking the chance that they
will be turned off by something completely irrelevant to your
demo.
</code></pre>
This..
Now i have bunch of meme-bros instead of useful colleagues.
I've been using LoadingReadyRun's Installation Anxiety sketch[0] as a guide to name computers around my house. I originally had a file server, so I named it <i>toilet</i>, then I had a web server named <i>gram</i>, and named my router <i>dishwasher</i>. I recently started a job where I get to run iventoy[1], so the computer it's running on is <i>paul</i>.<p>[0] <a href="https://wiki.loadingreadyrun.com/index.php/Installation_Anxiety" rel="nofollow">https://wiki.loadingreadyrun.com/index.php/Installation_Anxi...</a><p><a href="https://m.youtube.com/watch?v=ajW2fDy41fY" rel="nofollow">https://m.youtube.com/watch?v=ajW2fDy41fY</a><p>[1] <a href="https://www.iventoy.com/" rel="nofollow">https://www.iventoy.com/</a>
The way I've been naming computers for about a decade now is formfactor, intent, and architecture. So you end up with SBC-MUSIC-ARM, TOWER-SERVER-INTEL, LAPTOP-TEMP-AMD, and so on and so forth. It's great so long as you don't have more than about fifteen computers. For a while there were three desktops in one room all dedicated to rendering, so they received names that when read in order were a nod towards a certain film: 1TOWER-RED, 2TOWER-ON, and 3TOWER-YOU.
I use Star Wars planets for computer. Screen time of the planet roughly correlates to the importance of the computer. Home server is Tatooine, Linux laptop is Hoth, gaming desktop is Mustafar, etc.