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…
How do you tell managers that having good developers is a privilege?
51–60 of 123 posts
Re: How do you tell managers that having good developers is a privilege?
#52What 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…
How do you know his whole contract terms. It's not that simple, there might be an informal clause to it, agreed on with previous management. Maybe in lawyer-centric US this is unthinkable, but I doubt that. The country is not specified, btw.
Re: How do you tell managers that having good developers is a privilege?
#53I 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…
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…
But when you actually look at what it says, it's basically "roll over". The best outcome envisioned in that response is, "If he compromises and lets you have a bit of flexibility". First, take a moment to appreciate that *lets you have" remark. As if we are grade schoolers and the manager is a teacher who gets to decide when we go to the bathroom.
Then notice how the best outcome imaginable is a compromise. A scenario where you simply get what you want is not even on the table, here, even though it's entirely possible that getting what you want in this case is the best outcome for everyone involved, and at the very least is probably achievable and reasonable.
Really, this is something that you can't properly advise on without knowing the personalities and the context. If management is full of dickheads, then this is your signal to search for the exits. Start looking for a new job, and jump ship when you can. Things will only get worse. On the other hand, if management is generally reasonable and this is an isolated problem, a reasonable discussion with this manager to find out what's going on is the thing to do. But this should be a discussion between equals, not the groveling and tiptoeing suggested.
Re: How do you tell managers that having good developers is a privilege?
#54I would find to cleaner to sign contract for 6 hours a day instead of 8 hours a day one and then slack away the difference. Is it possible that manager there is trying to change local culture?
Second thing that bothers me is the "any expectations of us, beyond that we produce quality software according to schedule" part. So, he works in a company that makes over-estimates work. That is unusual and something to be thankful for, but I do not find it "fair" to abuse the situation.
If we buy that argument, then manager is in perfect position to pack schedule much more in order to keep them there as long as he wants. My opinion is that management that leaves some room for unexpected problems in schedule someone to be treasured and not taken advantage of.
Re: How do you tell managers that having good developers is a privilege?
#55I 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…
Going through the comments older than yours, I think you're significantly misrepresenting them. Very few of them are about punishing the manager. Most of them are about 'prepare to leave' or 'just leave' - the focus is on bettering the individual, not leaving a vindictive mark. In fact, on another review, there is one deleted comment whose content I don't know, and none of the other comments are about punishing the m…
You can't tell them: They can only learn this through experience. Alternately they may be the sort of shop where average developers are perfectly satisfactory.
read: The counter-party to your negotiation is not an honest/competent partner who may have reached a rational conclusion given their understanding of the situation. Also, exceptional talent doesn't need to be treated like this. Conclusion: only average talent negotiates, compromises, respects management's motives. Exceptional talent finds a different party.
You don't tell somebody such a thing. It would never work. The rules are the rules to most people... It's not always better to have "great" engineers - often companies just want somebody sitting at their desk ready to act on instructions. If that's the case then there is probably a lower-skilled engineer that would count themselves lucky to be sitting at a desk for 8 hours. He will be a lot easier to manage and probably a lot more appropriate for the new management.
read: Management is hidebound and petty. No possibility for compromise exists. Management placing burdensome demands on your time, therefore, is not an opportunity to negotiate but a cause to leave. Tolerance of such a situation is for low-skill employees only.
It's called an exit interview. Once you secure a new job, don't be shy with your managers about why you are leaving.
read: Don't try to constructively engage your management. Exercise your opportunity to leave, and then, once your exit is secure, air your displeasure with policy changes.
You don't need to tell them anything. If you're a good developer, you choose where and with whom to work. Feel your power and use your power.
read: Obviously management has no legitimate concern here, or interest in expressing how employee time is structured.
You quit.
By not continuing to work under managers that are shitty.
---
I could go on. I may have miscounted on the ratio, but it's hardly "none-to-one"
Re: How do you tell managers that having good developers is a privilege?
#56Basically you tell the manager straight up. But as we are talking about a shity manager. They would most likely become offended and hate you or fire you.
Re: How do you tell managers that having good developers is a privilege?
#57I 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…
Re: How do you tell managers that having good developers is a privilege?
#58What 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…
Whether pay or conditions, there is nothing wrong with having a discussion and asking for changes (or in this case, retaining the status quo).
I do agree that "having good developers is a privilege" is a strange viewpoint. In fact, people often say I could get 30% more easily" when that isn't the case. So I take most of this question with a pinch of salt.
Re: How do you tell managers that having good developers is a privilege?
#59This situation is simply about a mismatch in culture, expectation and personal value.
The company would be better off finding developers who are excited to be a hacker at the company and wants to contribute as much as they can.
The developer would be better off finding a job that allows the freedom he wants. It's clear to me the developer values freedom over pay and he should find a company with the same value.
Trying to get the developer and management to meet in the middle will simply prolong the agony.
Re: How do you tell managers that having good developers is a privilege?
#60I 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…
One thing I've learned on the employer/employee side of development (that was initially painful, but now just seems obvious) is that for most software projects as long as the goal is well defined and meets some need in some market as well as expected, all they do need is mediocrity. And I mean this is the sincerest way, not the "fuck them for thinking this" way, but the "they are right to think this" way.
You could be a 10X (or whatever shorthand you want to use for 'very good') developer compared to everyone else on the team and you might feel yourself being Harrison Bergeroned by process, tools and management designed to pull everyone toward the middle and when you quit you'll think "Now they'll see what they are missing", but then you find out they could in fact easily replace you with mediocrity and nobody would notice and the project could even go on to be financially successful if everything else falls into place.
I highly encourage all developers to maximize their talent and ability and always keep learning, but at the end of the day the results I see in the real world (on both ends -- mediocre developers becoming wildly successful and extremely talented developers who don't do nearly as well financially) are that the correlation between pure talent/skill and their financial/career success relative to other developers is fairly loose.