Live data from Hacker News

How to Pay Programmers Less (2016)

yegor256.com

21–30 of 64 posts

Re: How to Pay Programmers Less (2016)

#21
post #16

>Warn them or even sign NDAs prohibiting any talks about wages, bonuses, compensation plans, etc. Isn't this actually illegal?

might depend on the state but for sure illegal in most. At the same time, I've never heard of it being litigated, ever. Usually the people told not to talk about their salaries are making the most.

"Usually the people told not to talk about their salaries are making the most."

Oh buddy, I hope you didn't fall for that one.

Re: How to Pay Programmers Less (2016)

#22
I think what is forgotten is: make programmers work less!

And I can't stress this enough, just how much work in both "dotcom type" companies and corporate IT goes completely to waste.

N out of 10 software features some smart "requirements manager" manager, or an artsy type "product manager" make up usually end up as ballast.

I'm saying that to highlight that the prime majority of companies spending pennies on devs are almost as a rule pathologically inefficient, and that is the root of their problems.

I think there is a wrong image of tech companies among the rentier types as a maintenance free cash cows, and that they can pick a well performing companies, fire all devs, but the "maintenance crew" and secure their retirement in a few years. My own experience with that is a complete opposite:

Companies with well selling tech products only do so for as long as they give good support, and keep money burning on marketing. The moment the rentier type buys the company, and cuts both new developments (which in reality usually are support, and bugfixes) and marketing, they really destroy the only things that were keeping the business going.

Re: How to Pay Programmers Less (2016)

#23
post #9

Don't forget free lunches. $10 bucks for an extra hour of productivity.

Yeah. 12 months in to a job there was a big push to move to the cloud, all devs go on 24/7 mandatory support. You would be required for a week to be on call, rotating in your team, so every 3-4 weeks depending on devs in the team.

For this you where required to always have internet access, return a phone call within 10mins to acknowledge a issue then be investigating within 20-30 mins. This means for 7 days if you wanted to drink you could not, you could not travel to a place without phone signal, you always had to have a laptop and phone on you. Essentially your personal time was not personal time, you are severely inconvenienced and for 168hrs you where essentially at work. For this you got 200AUD extra in your pay packet minus tax. It was non negotiable, this was no small company but at the time a recently IPO’d company with a shit load of cash. If you look at it as 168 hours for the week on call due to loss of personal time it’s a massive pay cut. I would of come out significantly ahead working minimum wage for just the sat/sun and loose less personal time.

Discussing it with my managers how I did not want to loose personal time and was happy to do it for free on a best attempt I’ll answer a call if I get it and available vs being absolutely available and accountable resulted in “but you get free lunches here, take it for the team”, the perks where used as leverage. As you said the cost of lunches to the company was peanuts, worse than that I had special dietary needs so never utilised it.

Didn’t stay long after that

Re: How to Pay Programmers Less (2016)

#24
Another good trick is to pass blame diffusely upwards. If you believe that your boss is fighting as hard as he can do get you the raise he 'wants' to give you, but the powers that be above him is blocking it, then you'll be far more accepting of the fact that you didn't actually get that raise. Hell your boss might even be 100% genuine in his desire to get you that raise, that's even better.

Re: How to Pay Programmers Less (2016)

#25
post #2

This is very true. I've worked for several employers like this. Usually it's better to quit but sometimes it's still worth staying because some jobs can open up more opportunities. In these situations, the best you can do is build leverage by creating direct relationships with stakeholders (e.g. clients and investors).

The whole of the Scrum methodology - funnelling all access to users via the “product owner” - is explicitly designed to disempower both end users and developers and concentrate power with the project managers and other managers. That’s why it’s so popular.

Even better some developers have even been brainwashed into thinking Scrum is for their benefit!

Re: How to Pay Programmers Less (2016)

#26

>Warn them or even sign NDAs prohibiting any talks about wages, bonuses, compensation plans, etc. Isn't this actually illegal?

Maybe. The NDA re: wages. It might be against public policy because it prevents employees from collective bargaining (union activity).

The other "agreement not to hire competitors' employees" stuff is definitely illegal under the Sherman Act it's both the basis for a lawsuit and criminal.

Re: How to Pay Programmers Less (2016)

#29
post #5

> Brainwash them regularly by communicating how great your company is, how big its mission is, and how important their contribution is. A few year ago a friend was working as a consultant for Disneyland mentioned about how little Disneyland would pay its lowest rung employees who kept the place running. Instead the workers were fed corporate bullshit about how lucky they were to work at the "happiest place in the wor…

It does not work on people who are not intellectually challenged (that is, take a moment to think - many low rung people cannot afford one) if the culture does not value this kind of conformity. (Such as not Asia.)

Keep them amused and distracted with addictive technologies and substances and the majority won't notice. Asia is no different from anywhere else.

Re: How to Pay Programmers Less (2016)

#30
post #4

Additionally when they treat managers as other engineers - meaning that they want to discuss changes or improvements without judging others for their ideas - just decide for them and announce your decision to show who is in charge.

"just decide for them and announce your decision to show who is in charge."

That reminds me of a conversation I had with a CEO once when I was a VP Engineering:

Me: "I think we have the scope of the new version pretty well understood by everyone and things are looking good for delivering on time"

CEO "I know for a fact that you don't understand the scope"

Me: "Pretty sure I do"

CEO: "Well I've decided as things are going so well we can add a few additional features"

Me: "Arghhhh..."

NB This was a while ago - my rookie mistake was having everything under control and everyone working calmly and productively and letting the CEO know, whereas the CEO favoured the "everyone must be near to panicking at all times" school of management.

Edit: Of course the features he mentioned were daft and were never implemented - he wasn't actually interested in them, just in unsettling me

Post reply on HN