F*@% Off, You’re Fired!

Let me tell you my story. I worked for a family owned construction company for 8 years, ever since I was 18. It was started by my dad, who then employed my siblings. About 10 years ago, they fired my dad and took over the company. I never understood why. I then began working for them when I left school. I never bothered to get my apprenticeship in a trade, yet learnt the ropes with them, and was advised I didn’t really need one. Then about 2 weeks ago, after many years of friction with one of the brothers, I was given warnings about improving my work habits or go look for a job elsewhere. (This was around the time I was suffering from clinical depression mind you) Then one day at work after a minor mishap I was told quite bluntly “F%$@ off, your fired! Get out of my sight!” Needless to say this couldnt have come at a worse time, especially since Im a homeowner. So lesson to the wise, get an apprenticeship, no matter who you work for!

VN:F [1.9.22_1171]
Rating: 4.4/5 (7 votes cast)
VN:F [1.9.22_1171]
Rating: -2 (from 8 votes)
F*@% Off, You're Fired!, 4.4 out of 5 based on 7 ratings

This post was submitted by One Angry Dwarf.


One Response to “F*@% Off, You’re Fired!”

  • Danny Says:

    Any family owned business where they fire the dad, there’s something not right with that. Sounded like they got greedy and wanted the lion’s share for themselves. If you had years of friction with them and knew they fired your dad, and weren’t going to care about your depression, you knew they put business above family. You’ll be fine, get through this, get the apprenticeship at some point (I’d work with their competitor), and hold tight. And talk to your dad.

    VA:F [1.9.22_1171]
    Rating: 0.0/5 (0 votes cast)
    VA:F [1.9.22_1171]
    Rating: 0 (from 0 votes)

Leave a Reply


Warning: Unknown: open(/home/content/37/3530237/tmp/sess_b2akg7cdpgacdlm11cjf4p5eg4, O_RDWR) failed: No such file or directory (2) in Unknown on line 0

Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct () in Unknown on line 0