Joined May 2011
·
Achievements
50 Karma
0 Total ProTip Views

Charity
Fork and commit to someone's open source project in need

Walrus
The walrus is no stranger to variety. Use at least 4 different languages throughout all your repos

Mongoose
Have at least one original repo where Ruby is the dominant language

Forked
Have a project valued enough to be forked by someone else

Raven
Have at least one original repo where some form of shell script is the dominant language
This is such bad advice. It certainly doesn't scale. Renaming a server is trivial, and as hrabbit said, significantly re-purposing a server without re-installing is a terrible idea that should never happen outside of a development environment. If you're using configuration management (and you should be), you can re-install a server back to it's current running configuration in minutes.
Name your personal workstations something cute. Name your clusters (if you have a handful of them) something unique or memorable, Name the actual servers after their purpose, a number and the domain. Eg. Not 'mercury-zeus.mycompany.com' but db1.zeus.mycompany.com.
At the very least, it makes on-boarding new people much easier, and it makes the monitoring alerts make much more sense.