Yes, so we did the typical Indian thing.
Wife and I. Another couple. Four of us Indians... headed to Niagara falls. Memorial day weekend.
DARNED! The whole place is full of Indians! Where did so many Indians come from! Did all the Indians in the US decide to descend in that weekend? From what I hear, that's not the case. Niagara is a perennial spot for Indians.
Apart from the plethora of Indian restaurants, what really "blew me" - was the fact that you would see not only the American and Canadian flags, but also the Indian flag flapping in the wind.
So where did so many Indians come from? Why at Niagara? Well I have done some investigations, and have found that another natural wonder - the Grand Canyon - is also overflowing with Indian tourists.
In another blog, I found a theory about two types of Indians - 1. A bunch of guys who decided to jump in a car and go to Niagara. 2. A married Indian husband bringing his wife and parents (possibly in-laws) to see the falls.
I believe there exists a third group - the newly married Indian who wants to show his wife something spectacular. I belong to this group.
So by this time, it should be an established fact that there are a lot of Indians at Niagara. I'm not particularly proud of my nationals swarming the holiday spot... but here's something I found snooty - there were language translations into French and Spanish, but there weren't any translations into Hindi or any of the Indian languages. I can understand the desire to be hospitable to Canadian neighbours coming to see the falls - but I can't understand how the large throngs of Indians are completely ignored in translating for the tourists.
Thursday, June 7, 2007
It's Promotion Time!
No, not job promotion. Code Promotion.
So I've been working on this piece of code for ages... first step is to get offshore working on it. Train them... explain the requirement... and how it is to be implemented. For no fault of theirs, they take a week. Darned, I feel I could've done it in a day! But that's human nature I guess - it always seems to be so much simpler than the task is.
Anyway, after all the review sessions, in the code goes to QA.
Manager is hovering over us... 'is it done yet' is the mantra he's chanting. As if that was not enough, he also passes some other tasks onto my plate.
Nonetheless... QA starts on the testing... no, they don't understand the system too well. They come back to me - 'can you run a test on our environment please?'. Innocent and sweet is they way they ask it... but innocent and sweet the request is not. The environment is warped, nothing is setup as it ought to. Finally I run an entire test run in their environment.
Yes, the test run includes a data refresh.
"Where's all our test data gone!!" whimpers QA! Well that was gonna happen if there's a data refresh!
And all the clients come pointing fingers... 'YOU! You are the one who erased all the data'.
"Dude! I was working on QAs request! They need to know what they are asking for! They need some ownership training !'
A day passes... "there's a defect #6845 assigned to you" says QA. The developers heart is in my mouth - "huh? me? a defect? OH NO! "
On looking it up... "pah -its a dud". That was no defect... working as planned.
Next day, another defect raised... That was no defect... testing not correctly done.
And so the day draws close... another release... full of the twists and turns that Information Technology includes... gets ready to go to production.
Will it make it okay in production? will it bomb? Only time will tell... not the QA sign-off.
Well only time will tell! With QA Sign-off, atleast I'm covered.
So I've been working on this piece of code for ages... first step is to get offshore working on it. Train them... explain the requirement... and how it is to be implemented. For no fault of theirs, they take a week. Darned, I feel I could've done it in a day! But that's human nature I guess - it always seems to be so much simpler than the task is.
Anyway, after all the review sessions, in the code goes to QA.
Manager is hovering over us... 'is it done yet' is the mantra he's chanting. As if that was not enough, he also passes some other tasks onto my plate.
Nonetheless... QA starts on the testing... no, they don't understand the system too well. They come back to me - 'can you run a test on our environment please?'. Innocent and sweet is they way they ask it... but innocent and sweet the request is not. The environment is warped, nothing is setup as it ought to. Finally I run an entire test run in their environment.
Yes, the test run includes a data refresh.
"Where's all our test data gone!!" whimpers QA! Well that was gonna happen if there's a data refresh!
And all the clients come pointing fingers... 'YOU! You are the one who erased all the data'.
"Dude! I was working on QAs request! They need to know what they are asking for! They need some ownership training !'
A day passes... "there's a defect #6845 assigned to you" says QA. The developers heart is in my mouth - "huh? me? a defect? OH NO! "
On looking it up... "pah -its a dud". That was no defect... working as planned.
Next day, another defect raised... That was no defect... testing not correctly done.
And so the day draws close... another release... full of the twists and turns that Information Technology includes... gets ready to go to production.
Will it make it okay in production? will it bomb? Only time will tell... not the QA sign-off.
Well only time will tell! With QA Sign-off, atleast I'm covered.
Subscribe to:
Posts (Atom)
Posts
