Ask HN: Anyone have process for creating good internal application names?
21–27 of 27 posts
Re: Ask HN: Anyone have process for creating good internal application names?
#22Re: Ask HN: Anyone have process for creating good internal application names?
#23Re: Ask HN: Anyone have process for creating good internal application names?
#24I was a 'corporate giant' a number of years ago and developing internal applications, and I always made a point of naming my applications with absolutely ridiculous names. A script for calculating the rate of employee attrition (voluntary departure) in Human Resources was named the "Quantitative Attrition Calculator" or "QuAC" for short. The icon was a duck. I always had a laugh when they said the name - some got the…
Because, as with a parachute... we were f*cked if it didn't deploy properly.
A tenuous link, but we still laugh about it now. And because of that, you would never forget what it actually does.
I can't believe no body has made this quote yet either...
"There are only two hard things in Computer Science: cache invalidation and naming things" - Phil Karlton
Re: Ask HN: Anyone have process for creating good internal application names?
#25I've used Star Wars planet names for quite a while, they sound good and most of them are pretty easy to remember. You should check Wikipedia's list: http://en.wikipedia.org/wiki/List_of_Star_Wars_planets_(C%E2...
Re: Ask HN: Anyone have process for creating good internal application names?
#26I was a 'corporate giant' a number of years ago and developing internal applications, and I always made a point of naming my applications with absolutely ridiculous names. A script for calculating the rate of employee attrition (voluntary departure) in Human Resources was named the "Quantitative Attrition Calculator" or "QuAC" for short. The icon was a duck. I always had a laugh when they said the name - some got the…