throwaway26960

They claimed to be damaged all throughout the complaint, yet didn't provide any evidence. Imagine explaining this to someone non-technical like your grandmother. You can make up a story and that non-technical person is going to have no idea if you are telling the truth or not.

The code change was requested by an employee and it wouldn't have caused any damage. Feature, not a bug. Imagine trying to explain this to someone who doesn't know what "code" is. It's just people making up a story to blame you. The point is that you can be blamed for anything you do and become involved in a frivolous lawsuit.

I told that to the Plaintiff, I'd just file bankruptcy, although they said they would still be able to garnish my wages. I assume the lawyer was not telling the truth, but you never know.

I'm proof that you can be sued for work that you do as an employee. Whether the Plaintiff will win or not is another story, but you can be dragged through years of the legal system.

They claimed it was an attempt to sabotage their company, yet they were the ones that asked me to make the change, jesus, FML.

Definitely learned my lesson on how important it is to get the initial contract correct, clarifying legal liabilities, responsibilities, etc. All your hard work and savings can go down the drain in a second if your employer wants to screw you over.

Got sued by my previous company for a line of code that they asked me to change. Luckily I had proof that they asked me to modify that line of code. If I didn't, well, I'd owe them millions of dollars and have my wages garnished for the rest of my life. Writing software is a bit ridiculous, your employer can blame you for anything and you'll have to waste years of your life and tens of thousands of dollars in the legal system.

Onto the next Javascript framework!

Tell your boss to give you a $10,000 bonus or you quit.

Because women are smart. The women I've worked with claim ignorance to programming, have no desire to learn programming, and give me a mile high task list of things to do. Then they take all the credit for my work while I'm being worked to the bone. I burn out and quit while they hire the next fresh programmer ready to accept work.

I've tried teaching employees to program, but when they realized how much painful/frustrating work they can now accept with this fresh new skill, they immediately stop learning how to program. Easier to give me all the work.

I don't think you can judge quality until you're actually employed. The best looking jobs on the surface turned out to be some of the worst jobs I've ever worked. There's a lot of similarities between dating and finding a job, heh.

Try applying for ~100 jobs a day instead of 2.

The interview process is great for employers...

1. Make qualified job interview candidate feel stupid by asking difficult questions unrelated to the job

2. Offer candidate low salary and argue that they barely passed the job interview

3. Profit

Best solution I can offer is to not play their game. You'll lose no matter how hard you try. You're better off studying marketing and psychology for job interviews.

I've found that the more time I spend doing low level code at my job, the less work they think I'm doing. The more you email and be at your desk, the harder they think you're working. I've realized that performance is relative rather than absolute, and if you're the only tech guy working in the office, there's no one to compare your performance against.

Just last week, they dumped a huge amount of server work on me. The next day, I told them I was working remotely to get the work done, and they get pissed. They make it seem like I'm taking the day off. Huh?

I wish the library was open 24/7. What's up with it only being open during working hours?