Office Check-in time

What is your work hours in office? Is it 9 to 6 job? Are you very much concerned about your check-in time? Coming office exactly at 9 AM and have plan to leave by 6 PM?

I am really very sorry about you Boss! This is IT industry. Here it doesn't matter at what time you are coming in office but for sure you will not leave office after 9 hours. It depends on multiple factors.

1. You can leave office at any time if you are on bench. But if your manager is sitting next to you or he is having very close eyes on his employees, then you have to spend complete 9 hours without doing anything.
2. You can leave office after 9 hours if you have work from home facility. But for sure you have to pick some call or attend some very late night meetings.
3. Bad scenario - You will get some crucial task exactly at 5 PM, and you will unable to complete it within 1 hour. This will happen very frequently.
4. If you client is US based(which is expected if you are in India), you have to support them at least until 8 PM.
5. The worst case is - You don't have work from home facility as well as your boss is coming late everyday. In this case better synchronize your timing with your boss, otherwise you will completely screwed up. If you will not do so then you will be in office by 9 AM, your boss will come to office at 12 PM, you will think to leave office by 6 PM but since your boss came late and he will also complete his 9 hrs, so he will leave office by 9 PM. And for sure he will make you busy till 9 PM.

Take care my friends & beware of IT Industry job.

If you have done some mistake, don't try to get it fix in future

I was always wondering how any one can mess all the automation code? Or how anyone can pass the testcase without doing any testing? And even that product get release in market too? All the time I can hear these kind of stories around me. I was from some other background and switched to testing almost 2 years back. Finally one day I got this "Brahm Gyan" when one issue hits me very badly.

"If you have done some mistake, don't try to fix it in future" this is what I learnt from my work experience as a Test Engineer. I have some genuine points for this. For example, suppose you missed some functional testing in very early days and you got that bug after few months. Mean while two-three RC/RTM cycles completed and since you missed that functional part in starting, so you thought like it is a part of this product itself(Even functional documents are also not available to verify them). And when you will be very much familiar with the product you find that issue as a bug. You raised that issue in-front of management, and that's it. All fingers will start pointing you, as you did a crime.

Yes! You are accepting that it was your fault. You are sorry about that. You want to get them fix ASAP. But the management is not looking for that, they are just wasting their time to pointing you. In-fact they got one "Bali ka bakra(scapegoat)". Even if any manager tell that this issue is existing from a long time, why you didn't logged a bug, it will be always your problem only. Not that manager's fault.

Moral : If you missed something while doing testing, never ever try to get them fix. Let it be like that if it is not affecting the product directly. After few years when you will quit the job then it will the problem for that new guy who will replace you.
This may applicable on the developer too.

Note : I know that I am ethically wrong, but that's what I learnt from this episode.