Office Hilarious

You can't circumvent the Manager 

Keeping the hilarious release on, I'm back here to share a witty moment with you guys.

After a diligent testing of of one of the bug fix, the fix was ready for the release. 

"Vicky will deliver the release on Monday and Somesh to provide training to Vicky as how to perform the release.", an email sent by Manager read such.  But this went surprising and bitter to Somesh as he was the only one and senior team member who was handling releases till date. 

However, Somesh completed his task, in extreme discord, he emailed to Vicky, "Go through the attached documents and in case you need more information feel free to ask me." at about 1.00PM keeping everyone in CC including Manager. God knows what happened that day.

Offended by this, Somesh didn't come office on Monday. Vicky had to deliver the code, he prepared release document and checklist and was all set to trigger the release. But to everyone's surprise he needed Somesh's ID to release as only Somesh's ID was mapped to the client network. No one ever even dare to look into such a serious matter. 

The issue was raised to Manager at about 11.00AM. And as per Manager's instructions, Vicky tintinnabulated Somesh's phone but Somesh was adroit enough to show his worth, didn't pick the call and in loosening temper, Vicky sent him a SMS. At about 11.45AM, Vicky received a message:"I'm at hospital. Will call you once I get free." 

Nothing could be done except to wait for a call. At about 2.00PM, Vicky received another message, "Call me". Somesh was at his best that day. Vicky along with the Manager ranged up his mobile and asked for his credentials. But Somesh said "No" and so Manager had to take the lead, Vicky cleverly put the phone on loud speaker.

Manager, "Hi Somesh, Lokesh here."

Somesh, "Hello Sir."

Manager, "As you know we have a planned release today and for that we need your credentials."

Somesh, "Yeah, I know but as per the client policy I can't share my credentials with any one. If you can send me an email regarding this, then I can send my credentials. Also, right now I'm at my home town, 260Kms away. I'm sorry."

Manager had no words or might be he was out of words except, "Thanks, Somesh." and cut the phone. 

WTF he said blunt no even to Manager, room was filled with such gossiping. Manager turned his eyes and left noticing that everyone is gazing at him, making fun of the moment. Somesh was King of the moment for all. Somesh had proved his worth.

At about 3.30PM, an email read,

"Dear Somesh,

 We have a planned release today itself and for this we need your credentials. Release must has to be deliver by today as we have already informed the client about this. You have to come to office to deliver the release as per client policy sharing of credentials is prohibited. Take this in your priority #1.

 Regards,

 Lokesh              " This mail was sent to everyone including senior manager.

And after 10 minutes, Vicky started delivering the release and we all were eagerly dying to see Somesh's face. Many of us even called him but he didn't pick the call.

Manager swaggered around and in triumphant voice asked to Vicky, "How's release going on?"

Keep smiling. :)

Note: This is a work of fiction. Names, characters, places and incidents either are products of the author’s imagination or are used fictitiously. Any resemblance to actual events or locales or persons, living or dead, is entirely coincidental.

Office Hilarious

Office Hilarious

Well, this started off as a part of my official voyage and I feel humble and honoured to have been a part and parcel of such “Escalated and Unintentional” humors,  humors which are jingle-jangling in my pocket.

So, let's get it started with the first one creaking louder...

Today, I have forgotten the description of all major bugs and what still resides in the tablet of my memory is a damn minor bug but severe enough to fuck s/w life of Somesh. 

We had a code delivery planned as per the schedule and team was overly busy fixing and testing the bugs to the quality. All major bugs were fixed and tested and minor ones were under progress. I got a bug to resolve and its resolution was to rename the text of one of the button to "Click the Button to  Select Employee" from "Select Employee". Wow, the luck was in my favor, what a bug I got to resolve! Hastily, I fixed the bug, performed unit testing and sent it to Somesh for testing. Somesh too had a luck that time, what a bug he got to test. After few rounds of black-box testing, bug was reported ok for release by Somesh.

After couple of days, build was released to the client for UAT and no bugs were reported by the client. Next day was full of congratulations mails by senior Managers followed by a savory lunch for the effort we had put in for this particular release in a short span of time.

But somewhere someone was envious of our success and one fine day, customer reported a defect mincing mine and Somesh's vocal chords.

The defect record stated :

"Severity - critical

  Priority - high

  Defect - When user changed the resolution of screen, text of button changes to
                  "lick the Button to Select Employee"

  Remarks - Such type of blunder mistake is not expected."

I hope this is enough for anyone to figure out what next would have happened to Somesh after this. My kind feelings for Somesh. 

Keep Smiling. :)


Note: This is a work of fiction. Names, characters, places and incidents either are products of the author’s imagination or are used fictitiously. Any resemblance to actual events or locales or persons, living or dead, is entirely coincidental.