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"

"To err is human", people say this, so do I agree.  Extending this a bit "To Err is to learn, and to repeat an Err is SIN". Contrasting to this serious statement,  here are my events below.

There are lot of pigeons around my home.  I like to watch them sitting on my compound wall.  As days passed by, the number increased gradually. So did they liked me, or not, I do not know. But they definitely liked my drying clothes to pee on. The interesting thing I came to know while talking to my neighbor is that pigeons do not pee on his clothes. I could not reason but I definitely thought  "This guy does not give you food,  but how can you pee on your master's clothes?".  There the problem lies, it is the pot of cereals which I keep for them. They flock in for the pot, and do whatever they want with my drying clothes.  I am not willing to take the pot off. I have to dwell with the problem, by adjusting myself to the issues which comes up. The problem propagates and we live and learn.

Two days back, I had a swollen left palm due to some freak accident at home. It was very difficult for me to grip using left hand. Though I got my motor bike to commute to office mostly driving in one hand. On way back home, I was supposed to apply sudden break, but ended up breaking left mirror of my motor bike. The problem propagated when I dropped vessel containing milk. Adding more problems to the list.  It is not necessary that we have to err and learn. Most errors are because of negligence and over confidence.

Whenever I forget to close a window, It rains heavily and next morning, my room is a swimming pool. Whenever I start cooking, I get a call. After answering a long call, it is a havoc at kitchen. Whenever I wash my motor bike and keep it clean, it rains the next day, to make sure that my bike is a dirt bike.

Now it is "To Err is Sin". Propagation of error is everywhere not to mention about our own softwares. It is a crazy world where people are paid to err, propagate the error.

Here is the error reported while I was using Valgrind for sample program which is coded for 900 LOC.


==25984== More than 30000 total errors detected. I'm not reporting any more.
==25984== Final error counts will be inaccurate. Go fix your program!


No developer would like to read such Error. While reporting error do you want to

1. Mock the developer
2. Frustrate the developer



The Sole purpose of error reporting is to convey the information that your deed is wrong and may be harmful, or it may help many others if corrected. There is a mutual dependency. One end wants things to be corrected and other end which should introspect the causes of error and correct it if it is apt. Therefore it becomes very important as how the error is presented. Error should be presented in a very polite manner. No would accept "You have done a mistake" but they will correct by themselves "You might have done the mistake because of so and so reason".