Last post was thought upon Mistakes, Errors or whatever. After a long day coding,  I was supposed to compile and "Check-In" the file. The "Makefile" which compiles has a problem, though not self-induced. It does not remove the object files, if the compilation fails. Instead of fixing this problem, I calmly removed the object file and re-compile. The problem has already propagated, I am spending time to remove the file. There are two windows, one does the compilation and other fixes the problems of compilation. Now this how it goes

$ rm file.o        #Remove the file
$ gcc ..... file.c #Compile it
$ rm file.o        # Remove the file
.
.
$rm file.c        

Grrrrrr...a blunder. Instead of removing object file, I had deleted my long day's hard work. No backup of the file and just I can say "what the hell". Identifying another problem in the course, "Always keep source directory different from compilation directory". Anyway we do not learn from some mistakes. Coding at the rate of 70 wpm, I am not comfortable with numericals keys and their shift counterparts. I have this problem of saving the file with different names, because of another mistake. Command to save ":w!" sometimes will be typed as ":w 1" or ":w ~", thus saving the file as 1 or ~. Luckily I had done this mistake. The file was saved as 1. A boon which saved my day because of this mistake.

Postulating the entire things,  and comments by inspirethoughts  on Murphy's law.
"A right must always go wrong"