Timeline for How not to get fired within 6 months?
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 27, 2021 at 3:43 | comment | added | nick012000 | @Job_September_2020 "In fact, if you only work exactly 40 hours per week and say "NO" when the boss asks you to do extra work, you will get FIRED in the business world." Maybe in America, but other places have actual legal protections for the workers. For instance, in Australia, it's actually illegal for a full time employee to work more than 38 hours per week on average. | |
| Jun 25, 2021 at 18:03 | comment | added | Job_September_2020 | @Daniel R. Collins, No need for me to change my answers because they cover all the bases for many REAL WORLD scenarios including the OP's situation. You can't work 40 hours per week and go home at 5:00 PM, and then expect to get promotions. In fact, if you only work exactly 40 hours per week and say "NO" when the boss asks you to do extra work, you will get FIRED in the business world. Plain and Simple. That is how the real business world works. | |
| Jun 25, 2021 at 17:56 | comment | added | Daniel R. Collins | -1 Currently for keeping the incorrect interpretation of the "5 minutes" at the end of the answer (confirmed by OP). Happy to upvote if that gets fixed. | |
| Jun 25, 2021 at 17:45 | comment | added | Job_September_2020 | @Daniel R. Collins, If the boss asks a worker to do a task that takes an extra hour after 5:00 PM, then the worker can ask him if the worker can do that tomorrow. But, if it's an urgent issue that a BIG customer is waiting, which could result a big sale or not, the worker should stay and work on it (and he can take off 1 hour tomorrow). In the business world, to be successful, often workers should be willing to spend extra time on unexpected tasks due to business requirement. For example, most software engineers work about 50 to 55 hours per week (and NOT 40 hours per the official contract). | |
| Jun 25, 2021 at 17:23 | comment | added | Job_September_2020 | @Hdg, If your merging code issue blocked the work progress of someone else in the team, i.e. someone else is waiting for your new working code to test his module, then I guess your boss may have a good reason to ask you to fix it ASAP so that the next day the team may continue the work smoothly. In my experiences, most bosses are reasonable and they would let you fix the merging code issue the next day if the delay does not prevent the team from working the next day. | |
| Jun 25, 2021 at 8:34 | comment | added | Hdg | Thanks for your detailed answer. Daniel is correct, there was only 5 minutes left till I finished work for the day, but my manager asked me to do something involving source control that would take well over 5 minutes (he wanted me to push a commit but that code had merge conflicts that take a bit of time to resolve). I had a commitment I needed to leave for immediately when work finished, and I gave this as a reason to my manager. I think I also suggested I do it when I'm back in work the following day. | |
| Jun 25, 2021 at 2:04 | comment | added | Daniel R. Collins | I think the "errand" issue wasn't something that was going to take 5 minutes. It was a commitment for which the OP had to leave work on time that day, vs. a work task that would take them past their quitting time to finish. Suggest editing that part of the answer. | |
| Jun 25, 2021 at 0:11 | history | edited | Job_September_2020 | CC BY-SA 4.0 |
deleted 8 characters in body
|
| Jun 25, 2021 at 0:04 | history | edited | Job_September_2020 | CC BY-SA 4.0 |
deleted 8 characters in body
|
| Jun 24, 2021 at 23:41 | history | edited | Job_September_2020 | CC BY-SA 4.0 |
deleted 5 characters in body
|
| Jun 24, 2021 at 23:35 | history | answered | Job_September_2020 | CC BY-SA 4.0 |