I Once Worked for Someone Who Doesn't Pay and Treats His Employees Like Crap

I worked for a terrible manager. He created a hostile work environment, and doesn't know on how to even run a software company, blaming his programmers for failed products. So this is the story of how things went, and I hope you guys never come across someone like him.

You might, ask why did I start working for someone so terrible? Well, I needed a job. I was convinced that I should work for him because he hired a programmer to build a product that shipped. He also had a nice, trendy looking office in Downtown Vancouver.

But despite that, he was a terrible manager. I can't believe I was able to take his crap for eight months.

There was a side of me telling me that I'm just a terrible programmer, and another side telling me that probably the manager was right, and maybe there are some ways to win myself back.

But nope, I learned that the hard way. This guy was a total ass hole boss, that lacks even the most basic critical thinking skills. His way of managing is no more different than a fortune teller with a crystal ball. If there is something that he doesn't like, he won't analyze, but instead react instantly, based merely on intuition and no thought was put into his action.

## My Eight Months Working for This Guy

I started my first day along with another guy. I was the programmer, he was the designer. First day or not, it was an orientation, and because it was an orientation, the boss decided to not pay for it. I found it odd right there.

And, on the day of the orientation, he set out rules for us. And the rules weren't the fluffy, make-you-feel-good-inside rules, such as "we come to work all happy and joyful, and we will have lots of fun and we will learn a lot." It was fluffy, but it made you feel like crap hearing it.

This was his first rule: there is nothing you can't do; there's no complaining. Everything the customer wants, you must be able to do it.

And then he contradicts himself by putting out this second rule: there is no bullshitting. He litterally pulled the verbified form of the s-bomb, and prefixed it with a noun to describe a male cow. I'm not kidding you.

So, I already started having doubts about this guy.

Then comes my second day at work.

I started doing the regular stuff, building up the company's web page, adding in some sample projects me and the designer had done in the past--also an odd thing to make us do.

In the middle of the day, I hear the boss exclaim "oh my god! She actually sent out the emails as Cc and not Bcc?"

He then makes the phone call to the person. And man was it ugly.

"Hey, I saw the emails you sent out," said the boss "you're supposed to Bcc, not Cc! Don't do it again!"

He then ends the call. "Stupid girl," mumbled the boss.

"Why?" I asked the boss.

"There was another organization that I worked with," said the boss "we sent out emails, and sent them with Cc, and not Bcc. The people being Cc'ed weren't too happy."

I was still skeptical that that was a good enough reason to spazz out at a someone in such a manner. Regardless, I didn't have much of an idea what all of that was about, because that girl wasn't an employee at the company, but was part of another organization, that the boss is involved with.

For the next few weeks, we work on our first few websites. Those went smoothly.

But the boss decides to have a change of plans, and wants to build a product that competes with HootSuite.

He wanted to get it done in four weeks. And all of the features done, perfect, no mistakes.

It wasn't the schedule that bothered me, but the details he put into it.

There is nothing wrong with that either, but he wanted everything to be done by the four weeks time schedule. As if there is absolutely nothing wrong that can happen. As if I am an encyclopedia of the DOM API, the perks and quirks of all browsers, and a plethora of back-end technology that will allow me to come up with the perfect solution to the problem, in a short amount of time.

Well, things end up not going as planned. Fou...