Live data from Hacker News

How do you tell managers that having good developers is a privilege?

workplace.stackexchange.com

91–100 of 123 posts

Re: How do you tell managers that having good developers is a privilege?

#91
post #14

What a bunch of spoiled, whining brats! Sure, you can only code for 4-6 hours a day, but why not honor your contract by spending that other 2 hours mentoring less senior people, trying to understand your employer's business goals, and generally trying to do your best to move your company ahead. Sheesh. By the way, the sheer arrogance of the question "How do you tell managers that having good developers is a privilege…

> I believe that as a programmer, it's your duty to spend some time doing stuff your manager didn't know he needed to ask you to do, rather than running personal errands.

--------------

I believe in dealing in good faith with people who deal with me in good faith. But it has nothing special to do with being a programmer; it's something I'd do in any job, and it is reciprocal. There's an implied agreement that they're going to try to treat me decently and there's an implied agreement that I'll do the same for them. If either of us breach that, I strongly desire the other party to defect.

Re: How do you tell managers that having good developers is a privilege?

#92
The original asker of the question wrote exactly what he should say to the manager, right into his SO question. It's this bit:

> The reality is that any of our senior developers can walk out the door and have a new job with as much as 30-40% higher pay within a week. Most of us are only staying here for the casual environment, and being able to mix personal time into our work days.

He should just say that. If it's really true, then he should feel comfortable leveling with his boss like this.

Re: How do you tell managers that having good developers is a privilege?

#93
I handed in my notice recently. My situation was somewhat similar to the one of the poster: project really not that interesting, unglamorous company, so-so salary, but casual atmosphere and not much to do, and I got to keep a lot of energy available to study and pursue my own coding projects. Then there was a change in management and pressure went up tenfolds, so I resigned.

First, I recognise now that it's potentially a bad idea to keep a job just because it does allow you to coast. There's a depressing quality in such choice; work representing the most part of our day, underperforming by choice, by remaining in an undemanding job, can even lower our self-esteem. I didn't do me much good, in any case.

Secondly, I am leaving because the market allows me to do it, because I know I am likely to find something better in a reasonable time. I could have handled the pressure, I could have remained and try to make that place a better place, but it's simply not in my best interest and it did more sense to just quit.

The position of the poster baffles me a bit: he recognises that conditions have changed and instead of adapting or refusing the new state of things, he dumps his responsibility to his own happiness to someone else: his manager. Indeed having good developers, in the current state of the market, is a privilege. In five years or ten years it might not be the case. Why making a case of us vs them? Isn't simpler to just take advantage of the bull dev market and leave?

It's naive, but widespread, from the part of managers to believe that by increasing the pressure they will get more bang for their buck. Let's them learn the hard way, until we can afford it. To moan and not budge is almost suspicious - maybe the poster is not so sure of himself after all? - and counterproductive for every party involved.

Re: How do you tell managers that having good developers is a privilege?

#94

I find it very sad that the top answer on stack exchange is a guide for how to have mature discussion, see the manager's point of view and collectively look for a solution -- while respecting his authority. But when you come to HN, 10-to-1 the comments are all about punishing the manager by leaving, teaching management a lesson, suggesting that maybe they only need mediocrity (in other words, developers as great as u…

The top-level answer is all the fluff without the substance. It is just nicely written.

The real answer should basically say that you need to start negotiating.

Of course you need to be nice and civil (read Dale Carnegie's book) but also understand that you don't need to liked by some people. For negotiating there are many books. But the point is basically very simple: 1) figure out what you really care about, 2) learn what other side really cares about, 3) be nice, 4) every negotiation needs to end with both parties satisfied, 5) "no deal" is also possible outcome

Re: How do you tell managers that having good developers is a privilege?

#95
post #24

Earlier quoted context omitted.

I didn't personally find it very mature. It's just somebody parroting "How To Win Friends" with an authoritative spin. I found it manipulative and warped. This guy isn't happy with being told what to do. A conversation is very unlikely to sort this out. I don't think leaving is about "punishing the manager." This job will be more appropriate for somebody else, and this company will probably be better off with somebod…

This job will be more appropriate for somebody else, and this company will probably be better off with somebody happy working in the new environment. If several senior developers leave because their attitude is not a good fit for new management, then the company may have to hire and then train new staff on loads of bespoke stuff without the people who wrote it being there. Who cares about getting people who fit the c…

It appears you've learned the lesson, having developers that write working software results in a more profitable company than having developers who remain in their seats for 8 hours a day.

The key is to make the company culture fit those who write working software.

Re: How do you tell managers that having good developers is a privilege?

#96

I find it very sad that the top answer on stack exchange is a guide for how to have mature discussion, see the manager's point of view and collectively look for a solution -- while respecting his authority. But when you come to HN, 10-to-1 the comments are all about punishing the manager by leaving, teaching management a lesson, suggesting that maybe they only need mediocrity (in other words, developers as great as u…

generally espousing a naive us-versus-them attitude. It is nearly impossible to avoid this kind of attitude when managers see themselves in a shaping rather than supporting/facilitating role. I've seen good teams given a new, inexperienced manager who sees his job as turning certain knobs and "incenting" certain behaviors and outcomes, and it ends exactly like you think it would. The good devs leave, and the team is…

It's also a great lesson for software development as having the Manager class instruct the 'managed' classes is usually a worse design than having the managed classes inform the manager.

Re: How do you tell managers that having good developers is a privilege?

#97

I find it very sad that the top answer on stack exchange is a guide for how to have mature discussion, see the manager's point of view and collectively look for a solution -- while respecting his authority. But when you come to HN, 10-to-1 the comments are all about punishing the manager by leaving, teaching management a lesson, suggesting that maybe they only need mediocrity (in other words, developers as great as u…

>But when you come to HN, 10-to-1 the comments are all about punishing the manager by leaving

It's not about punishing the manager, it's about getting the best job you can.

The problem, I think, was how the original question was phrased. It made it sound like a moral problem "You don't deserve good developers" which is a not very professional way of looking at it.

It's not your job to teach your boss how to do his or her job, and for cultural reasons, usually attempts to do so are met with hostility. The closest I have come without causing problems is buying my boss books. And even that... well, it was presumptuous, and it didn't change the boss' behavior, but it also didn't seem to blow back on me.

The question would have gone better if it were framed as an economic issue, a "what's best for me" issue, rather than as a "how can I change my boss" issue.

"I am getting paid less here than I think I could get paid elsewhere. That was okay before, because I am willing to take a pay cut to be treated a certain way, but management has changed now. What do I do?"

The problem here is that what the employee wants (and was sacrificing money to get) was a certain management style. If you want more money, you can negotiate that with your boss. If you want a new management style? you probably aren't going to be able to negotiate that. You could negotiate specific consequences of that management style, say, flex-time, but the root of it is still there. You probably aren't going to change your boss' management style.

In that case? A rational actor would leave the company. I mean, they would do so as gracefully as possible, of course, but you aren't going to change your boss' management style.

Re: How do you tell managers that having good developers is a privilege?

#98
Go over the manager's head. If that company is having trouble keeping senior staff, there are reasons for it and those reasons are probably not secret. I've done this, with mixed success, but have never had a problem with retaliation. You might be surprised how welcome your skip-level feedback is.

Oh, and if your skip-level manager doesn't know who you are (and ideally, his manager), then you either need to work on visibility, or you're not as senior or as pivotal as you might think.

Be polite. Tell them that you thought flexible hours were part of the deal.

And then walk. Moving to a new team in the same company is probably just as good, if you can swing it.

Re: How do you tell managers that having good developers is a privilege?

#99
post #22

It's called an exit interview. Once you secure a new job, don't be shy with your managers about why you are leaving.

I never do exit interviews because I don't want any burned bridges. Smile and wave on the way out and go on to the next place.

Re: How do you tell managers that having good developers is a privilege?

#100

Earlier quoted context omitted.

generally espousing a naive us-versus-them attitude. It is nearly impossible to avoid this kind of attitude when managers see themselves in a shaping rather than supporting/facilitating role. I've seen good teams given a new, inexperienced manager who sees his job as turning certain knobs and "incenting" certain behaviors and outcomes, and it ends exactly like you think it would. The good devs leave, and the team is…

I'm not sure what you mean. All managers are paid to ensure better outcomes, where "better" is defined by the company (not by the engineers, except insofar as this enables the company's goals). Some managers are more effective at this, and some less. As a manager, sometimes it's better to have a cohesive team with consistent rules, even if some engineers will opt to work elsewhere as a result. Although I am sympathet…

the manager would have no choice but to call his bluff.

It's exactly the same for good devs confronting a confused manager. They must call the manager's bluff, and that often (usually?) means leaving. Less experienced devs will try to push back, but it's probably as hopeless as the dev imagines it to be, and they risk just prolonging a bad situation.

Post reply on HN