Wednesday, May 26, 2010
Boredom of Frequent Innovations
Blogs , Tweets , Facebook, Orkut, My Space. All come up so frequently
Indian Groupism
Where ever we look into we can see "Group"ism in India. No matter , trade union, governments, offices , worship places, religion ,caste etc. It is basic instinct in every Indian to categorise / group people .
As per history , Indians has the unique classification of people based on their work . Which eventually gave way to caste system. Even though several other religions reined in India marginally, there also the differentiations remain not in form of caste , but grouped/categorised. You can see group in political parties, temples ,churches ,religion, mosques all in all. we group maoists and terrorists differently. We even group individuals as a group. We align people in single group lead by a leader. As soon as a group is formed a board of directors or director is also crowned , aimed to protect group.
Indians can easily identify the common features of objects/ subjects and create groups accordingly so that next time one comes , he wont have to wait much, till he is into a group. Group is visible every where, within school , colleagues, professors, educational system also. Group is also visible in relationships , within family, within sisters , within brothers, etc.
However the west & rest of the world seems to be different with what we have in groupism as per information.
The least place where we cannot find GROUPism is the Armed forces. However this might be because of less public attention / media coverage. We even group people based on immigration from nearest state also.
Thursday, May 06, 2010
The Spoilsport of '0'
"0" for which all Indians are proud of . Looks like we have much more affection towards 0 than ever before.
Illustrating a true incident.
I was in implementation team in one of my projects. There was a cluster installation of a product. Even though we crossed deadline due to sizing reasons, we were able to complete installation on first server [primary server] and remote database making it more complex. Key point was this was not been performed by anyone among us , so there was space for confusion & doubts. It was a great relief to see this complex architecture installation getting completed in primary server , there by creating creating database. With more than 18hrs spend in cordinating with different teams to make storage , server ,os, cluster ready, I thought of completing second installation too. But we were stuck with error .
"Secondary server is unable to find the primary server ".
For two weeks I & OEM was behind finding this root cause. Finally it has come to my notice that the hostname with which primary server was configured & the name published in DNS were different. The configured hostname violated naming conventions of company , so we had to redo installation again.
Instead of naming server as SYSTEM"O"1, Windows team by mistake configured it as SYSTEM"zero"1. But both looks same at first sight in system; SYSTEMO1=SYSTEM01 .
This remembered me of the story of spacing of "," taking a mans life.
"0" can make our life miserable this much.
Illustrating a true incident.
I was in implementation team in one of my projects. There was a cluster installation of a product. Even though we crossed deadline due to sizing reasons, we were able to complete installation on first server [primary server] and remote database making it more complex. Key point was this was not been performed by anyone among us , so there was space for confusion & doubts. It was a great relief to see this complex architecture installation getting completed in primary server , there by creating creating database. With more than 18hrs spend in cordinating with different teams to make storage , server ,os, cluster ready, I thought of completing second installation too. But we were stuck with error .
"Secondary server is unable to find the primary server ".
- I started debugging
- Windows team started debugging
- Case was logged with OEM
And no need to say all pressure on team
For two weeks I & OEM was behind finding this root cause. Finally it has come to my notice that the hostname with which primary server was configured & the name published in DNS were different. The configured hostname violated naming conventions of company , so we had to redo installation again.
Instead of naming server as SYSTEM"O"1, Windows team by mistake configured it as SYSTEM"zero"1. But both looks same at first sight in system; SYSTEMO1=SYSTEM01 .
This remembered me of the story of spacing of "," taking a mans life.
"0" can make our life miserable this much.
Subscribe to:
Comments (Atom)
