Meanwhile it would have cost $$ for both the downtime and repair cost to fix the issue before failure. Now that it failed it will cost $$$$$ to fix it as an emergency.
Or even better, they have money to upgrade their perfectly working computers and chairs, but they don't have the money to repair or change the tools you need to work.
Which is why you always get this sort of order in writing, from the boss. If they won't send it, you send them an email saying something like "Thanks for taking the time to discuss this issue with me today. Just to confirm, you said I should . I pointed out that this could lead to , but you stated I should continue anyway. Please let me know straight away if you don't agree with that recollection."
Bosses who wont send this sort of thing in writing, and who don't read emails you send them are handy, as you do things your way and just poibt out that you emailed them about it a week ago. The papertrail becomes your greatest asset.
Kinda. Had the CEO want some code changed while the VP of my department was on vacation. Changed the code, and the VP had a grudge against me afterwards because it was code he wrote. A year later a project failed (due to mismanagement) so it was blame game time and the devs got blamed and it was firing time. I didn't work on the project that ended in failure, I was working on a different project which was a success.
Guess who got fired?
I guess technically it was because the VP didn't like me. But the reason he didn't like me is because I did my job and made the software work the way the CEO wanted it to work.
That's just how she goes. Catch-22 scenarios happen no matter how likable you might be.
Was able to find some more details - it's the bucket of an RH340 excavator at the Poitrel coal mine in Australia, probably damaged while moving massive rocks about
Strange, it was built to very rigorous maritime engineering standards, which explicitly exclude materials like cardboard, paper, string, and cellophane.
Meanwhile it would have cost $$ for both the downtime and repair cost to fix the issue before failure. Now that it failed it will cost $$$$$ to fix it as an emergency.
Refuse to schedule maintenance and your equipment will schedule it for you.
Yeah but the top boss's friend owns a manufacturing company, not a repair company, so this policy comes from the top
Not to mention injury/death when the equipment catastrophically fails.
True, but sometimes the cost to repair the thing is irrelevant when the required amount of โdoneโ is what is time gated.
Shortly after they fire you and tell you that you shouldn't have done that. ๐
Or even better, they have money to upgrade their perfectly working computers and chairs, but they don't have the money to repair or change the tools you need to work.
Which is why you always get this sort of order in writing, from the boss. If they won't send it, you send them an email saying something like "Thanks for taking the time to discuss this issue with me today. Just to confirm, you said I should . I pointed out that this could lead to , but you stated I should continue anyway. Please let me know straight away if you don't agree with that recollection."
Good advice but what do you do in America? I'm not sure my boss can even write.
Bosses who wont send this sort of thing in writing, and who don't read emails you send them are handy, as you do things your way and just poibt out that you emailed them about it a week ago. The papertrail becomes your greatest asset.
Emojies?
If they like you, they won't fire you for any reason (almost), if they don't like you, they find any reason to fire you.
Jobs are not held or lost on merit, for the most part.
Kinda. Had the CEO want some code changed while the VP of my department was on vacation. Changed the code, and the VP had a grudge against me afterwards because it was code he wrote. A year later a project failed (due to mismanagement) so it was blame game time and the devs got blamed and it was firing time. I didn't work on the project that ended in failure, I was working on a different project which was a success.
Guess who got fired?
I guess technically it was because the VP didn't like me. But the reason he didn't like me is because I did my job and made the software work the way the CEO wanted it to work.
That's just how she goes. Catch-22 scenarios happen no matter how likable you might be.
God damn. Iโd love to hear the story behind this picture
Looks to me like the front fell off
Is that not typical?
Heck of a story
Was able to find some more details - it's the bucket of an RH340 excavator at the Poitrel coal mine in Australia, probably damaged while moving massive rocks about
The whole machine looks like this
Even with the door there that should indicate scale, that machine doesnt feel like its anywhere near as large as OPs picture.
Looks fine to me - the door seems to be about half the height of the bucket, which fits with the guy in the original picture
Oh yeah it looks fine, if you scrutinise it and measure it, but it doesnt feel fine.
Then don't look at the door...look at the bolt holding the bucket on the arm and the look at the size of the hart hat.
Big bolt
"hart hat"
"Big bolt"
Haha, awesome
Me too. I've worked extensively on open pit mines, and I've never seen anything like that in my time there.
I'm not an expert or even an equipment operator, but I've seen them break shit. Buckets are tough. One that big is very tough.
That would have been a fun noise.
The front fell off?
Strange, it was built to very rigorous maritime engineering standards, which explicitly exclude materials like cardboard, paper, string, and cellophane.
Metal fatigue ? Its just a scratch ๐
What monster of a HYEX has a bucket and arm that big? That is an absolute unit.
That dude is more flexible than I might have expected.
Shudders in sharp edges
Dragonslayer!!!
Aww haww