Naming
I've got a cold. I can't stop runny nose. So I don't go outside for a couple of days. I've stayed at home today. I kept thinking about some projects that I would start up this year. Especially, I was thinking about their names. I need to name them. It's so hard job for me.
It's naming. It's so troublesome for me. Don't you think that naming is quite a hard job indeed? Naming often troubles me. Actually, It takes me a long time. For example, when I make a program, I often wonder about the naming of the program, especially the names of methods and variables.
void doSomething(int i, float f) {
int i; // NG
int temp; // OK
float temp; // NG
...
}Concretely speaking, when I use the language "Processing", I hit the wall about the above soon. The names of the parameters are OK. But I want to use the same variable names "i" and "f" as local variable names. But it's compile errors. The language specification of "Processing" prohibits the double definition of variable names. We hit the same problem when we use many programming languages. We can't escape this problem.
Generally speaking, naming is so hard. For example, when you get married and have a baby, you must hit the naming problem about your baby. It's more difficult than naming one of the programs in "Processing".
By the way, I was impressed by the naming of the music brand of Eiichi Ohtaki. He was one of the most famous musicians in Japan.
He named his brand "Niagara". Niagara means the big fall in the U.S.A. and Canada. He didn't name his brand "The Big Fall". I think that he had a good sense of naming. He implied his name as "Niagara".
My name is "Amano". We Japanese can also pronounce "Ama" as "Ten" which means "sky" or "heaven". So I may use my project as "Sky" or "Heaven". "Sky" is commonplace, but "Heaven" is a little bit religious.
P.S. If you are interested in the naming issue in programs, you should read the book titled "Code Complete" written by Steve McConnell.