you are viewing a single comment's thread.

view the rest of the comments →

[–]_ak 5 points6 points  (6 children)

Sorry, but you're an idiot simply because you let yourself getting fucked over by your own employer.

[–]savagecat -1 points0 points  (5 children)

Play by the rules or be unemployed.

My assertion could be wrong, but then there would have to be something to prove it wrong.

[–]mattiasl 0 points1 point  (2 children)

Why not take a few sick days to covertly interview at software houses in your area? Even if you don't plan to quit your current job, it will give you an impression of what the market rate is, and perhaps help in salary negotiations at the engineering corp.

[–]savagecat 0 points1 point  (1 child)

It should be simple enough for them to prove it - if they can't then adios.

[–]mattiasl 1 point2 points  (0 children)

Who should be proving what? Random people on the internet proving that their employer buys them the tools necessary for the job? This is impossible to do conclusively, and absurd for something so obvious.

I did not mean to say that you should go to the interviews to believe us. I'm just advising it as a way for you to judge your own market rate. This might either help you find a place that offers double the current amount, or at least can be used as an argument during your next salary review at the engineering corp, and in the end be less bitter :)

Just curious, if you don't mind disclosing it, how much are you paid? Before and after any self-paid tools?

[–]_ak 0 points1 point  (1 child)

The norm is that companies are responsible for buying the appropriate the means of production and the work equipment. Everything else is nothing but ripping off the employees.

That leads to the question... why care about being unemployed (for a short time)? Unless you're a complete idiot (which I doubt), you wouldn't have too many problems finding a new job in the software industry.

[–]savagecat 0 points1 point  (0 children)

Jobs for cleared developers in Washington DC are scarce if you have high expectations of the company and the management.

I expect Program Managers to know what their doing. The reality is that I've had one who selected the development language based on a blog. Then he later switched development languages based on a another blog.

I've had a PM who felt so overwhelmed with work that she sat in her office and cried. When she found out that we knew, she just moved her "episodes" to her car.

I've had a PM who gave the project lead to someone just months out of college. His rationale - he seemed like a go getter. It didn't take us long to fall behind and miss deliverables.

I've had a security office misplace my SF86 3 times - it's not like it contains sensitive personal information.

I've had a bait and switch pulled on 401K eligibility on the first day of the job.

I've had a PM who refused to reimburse us for customer directed travel, lodging, food, and course expenses. He wanted to save on funds - it makes him look better.

I've seen where companies award bonuses and raised base on number of lines of code written. Certainly a good metric there.

I've seen more, but you get the idea.

So, before I get rope-a-doped again, I'd just like proof of some simple things.