One more thing I need to put is, if ever you have a goal and things dont go as they expect, stop and introspect, mistake is in your thoughts or actions, which may not be easily visible. But if you spend sometime you can reach what exactly is causing the trouble and preventing you from reaching the goal.
And if something catastrophic happens, and if you feel the mistake is within you, there will always be a fear to try again. But again mistake has to understood, lessons learned and do necessary course correction and next attempt has to be made.
The first part of reaching your mistakes is break down, the realization there is some mistake from your side. Not many can do it because they find justifications for their actions. Ability to introspect makes you a great human being and a path breaker. Ability to accept mistakes and learn from them makes you a human in true sense.
It's a personal journey, but you need courage to take it. Because the point is what gets revealed can break you or make you. It is not what you expect that gets revealed, lot of astonishing funda about you get revealed especially your biases, prejudices, ego and selfishness that has motivated the actions.
If anyone is interested they can start reading a book called " Blink " . Also you can take
https://implicit.harvard.edu/implicit/india/takeatest.html
It is a very interesting test, but be prepared it might throw some unpleasant truth about you also. So it is only for those who are open minded and can take the results with open mind and take both the pleasant and unpleasant results openly and have some time to evaluate them and take some positive steps for correction if applicable. I have personally taken this test 😃
Your thoughts are like software programme. If they are correct your goal will be realized as the communication with brains happens through our thoughts as neuron pulses. All thoughts matters conscious, subconscious and unconscious.
If a program crashes causing loss of lives or loss of business the question will come to programmer, tester and the quality auditor. Fun is the blame game. Programmer will blame tester, tester will blame programmer, both will blame quality auditor, auditor will show reports where they have told this application have bugs errors whatever. In short everyone wants to put on blame on everyone else telling they didnt do any wrong. Will put a personal experience also.
I still remember a project in 2006 for which I was the quality auditor. We have to do pre delivery checks before release. We have to test critical path. But I had the habit of involving myself with the team, doing occasional testing of all functionality even before it came for pre-delivery check. So sometimes I used to sit late night and all with dev team.
When new head came for quality she told doing too much testing is testing team's job and not QD's team. For pre delivery check QD only need to do critical path testing and fill the release check list.
So there was a release on one Monday. Friday I did some sample testing and told tester if there is any issue call me over weekend. He said fine. I also didnt bother to call him, as QD head had told extensive testing not needed also I had planned a party with my friends over weekend as some of us cleared a certification exam. Party went fine, weekend went fine. As planned I did the critical path testing and gave the release checklist.
Release went badly as client was angry calling even the CEO. Blame game went on with programmer blaming tester, tester blaming programmer, both blaming QD, our team telling we do this and we have done this. Finally fire fighting started and we gave the application.
But it had affected me deeply as a person. Yes the guideline was there, but I should have gone over weekend. I should have done some testing. Because the power to stop the release rested with me. I could have. For some days it was difficult for me to sign another pre delivery check, but I slowly got over it, trying to analyze where I went wrong in the previous instance including identification of critical path. I didnt think of the programmer who didnt do the right coding, or the tester who didnt test the things correctly, it was all about me and what I could have done in the given situation. I cannot correct their faults, but I can correct mine.
And that guilt stayed with me for over an year till I was able to stop a release by finding defects that the testing team was unable to find. Yes the communication went to customer on a delay in release, but the final release went smooth and lot of client appreciations came in. I got special award also from the account team. I have got many other awards in my life, but this award I keep close to my heart always as a professional. Because it was the result of introspection and course correction. It was also the proof of failure shouldnt put you down, fear shouldnt stop you, learning from mistake, you can over come fear and opportunity will present itself where your learning and experience will help you to shine through.
If you want to defeat Maya or perception you have to rise above it, you have to introspect. As rightly said by Saanjh Maya plays with your brains, your ego, Maya cannot touch your heart that sees the truth for what it is. Your ego sees first others and maybe others only when something goes wrong. Your heart sees first you when something goes wrong. Ability to point finger inward checking your mistakes is the first step towards winning over Maya or perception. Because once you do that, you dont do the things Maya expect you to do. You dont give Maya an opportunity to justify the crime. Maya will stand exposed as bad and mad. It is not just the girl, but the perceptions of everyone will stand exposed when one is able to rise above Maya with introspection. As everyone's ego will be killed.
Edited by shruthiravi - 8 years ago