top 31 comments

sorted by: hot top controversial new old
[–] 69 points 4 months ago (7 children)

Shortly after they fire you and tell you that you shouldn't have done that. 🙃

  • source
  • hideshow 7 child comments
  • [–] 26 points 4 months ago (3 children)

    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."

  • source
  • parent
  • hideshow 3 child comments
  • [–] 3 points 4 months ago (2 children)

    Good advice but what do you do in America? I'm not sure my boss can even write.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 9 points 4 months ago

    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.

  • source
  • parent
  • [–] 11 points 4 months ago (1 child)

    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.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 4 points 4 months ago

    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.

  • source
  • parent
  • [–] 60 points 4 months ago (4 children)

    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.

  • source
  • hideshow 4 child comments
  • [–] 34 points 4 months ago (10 children)

    God damn. I’d love to hear the story behind this picture

  • source
  • hideshow 10 child comments
  • [–] 27 points 4 months ago (5 children)

    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

  • source
  • parent
  • hideshow 5 child comments
  • [–] 11 points 4 months ago (4 children)

    Even with the door there that should indicate scale, that machine doesnt feel like its anywhere near as large as OPs picture.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 5 points 4 months ago

    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.

  • source
  • parent
  • [–] 14 points 4 months ago*

    Metal fatigue ? Its just a scratch 😂

  • source
  • [–] 14 points 4 months ago

    That would have been a fun noise.

  • source
  • [–] 10 points 4 months ago

    That dude is more flexible than I might have expected.

  • source
  • [–] 10 points 4 months ago

    What monster of a HYEX has a bucket and arm that big? That is an absolute unit.

  • source
  • Shudders in sharp edges

  • source
  • [–] 2 points 4 months ago

    Dragonslayer!!!

  • source
  • [–] 2 points 4 months ago (1 child)