TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

How to reward skilled coders with something other than people management

414 点作者 koopajah超过 10 年前

25 条评论

mathattack超过 10 年前
When I was at BigCo, they officially had 2 paths - one involved people leadership, the other technical leadership. The reality was technical leadership stopped a level below director, and only 2 or 3 even managed to make it that far. After 3.5 years there, it had a formative impact of pushing me away from both the company and technology. I recovered on both, but it&#x27;s something one should take seriously on taking a job. I&#x27;m not sure that creating &quot;Mega-consultants&quot; works either, as it takes the emphasis away from delivery ownership.<p>That said, here are a few ideas in rank order from easy&#x2F;feasible to crazy&#x2F;radical:<p>1) Technical leaders of a certain level can not be overruled on technical decisions by non-technical leaders in the department.<p>2) Encourage the best to share their work outside the firm.<p>3) Smart people like to be with smart people. Pay up for a culture or cohort of superstars, not an individual superstar.<p>4) Provide time and monetary budget for architecture and technical debt that is owned and allocated by the best in the organization.<p>5) Allow technical stars to have the ability to change assignments at their will with a given notice period. (Yes it may cause problems, but the free market is always giving them offers)<p>6) Enable managers to raise technical pay without concern for bands. For example, the VP should be able to say, &quot;I can hire 4 engineers for 100K each, or I can hire someone in the open market for 200K. Instead I will pay my internal superstar 220K since she will do it the best, even though it&#x27;s way out of bands of someone with her seniority and level.&quot;
评论 #8650797 未加载
zobzu超过 10 年前
One thing that always fails with that is that management always get more money.<p>Wanna be a tech leader paid 150k? (fancy title, +- same salary as before)<p>Or wanna be a director paid 250k? (fancier title, way bigger salary)<p>Kinda difficult not to choose the &quot;free tesla every year&quot; isn&#x27;t it? Plus.. the directory job is generally going to mean a more relaxed job (albeit less interesting for an engineer maybe, but that&#x27;s why you have open source projects right?).
评论 #8644747 未加载
评论 #8646595 未加载
评论 #8644630 未加载
评论 #8644634 未加载
评论 #8645281 未加载
评论 #8645353 未加载
jefffoster超过 10 年前
Whilst I agree that technical leadership is one aspect that skilled engineers can develop (and I agree that it&#x27;s important for all engineers) there are many more.<p>For example, developers can grow into great product managers. Some can deep-dive into a topic and develop by sharing that knowledge through conferences, blogs etc. Some are interested in the people management side of things (scrum, kanban etc). All of these (and much more) are incredibly valuable and increase the value to the company they work for.<p>The challenge for companies is to recognize all these degrees of value (and reward them appropriately). I did some work to try and capture this with a visualization called a skills map (<a href="http://blog.red-gate.com/skills-maps/" rel="nofollow">http:&#x2F;&#x2F;blog.red-gate.com&#x2F;skills-maps&#x2F;</a>). Any feedback greatly appreciated!
dmfdmf超过 10 年前
This is a problem not just for coders but almost any technical area. A loooong time ago when I was still in engineering I worked for Big Corp, Inc. and they had a designation for master technical talent, I forget the name, so let&#x27;s just call them Jedi Masters. It was a non-management path for those who didn&#x27;t want to go the management route but it recognized their value to the company. If you reached this level you had no manager and had no assigned work but people from other projects could come to them for advice, help, consultation, etc. and they could choose what they wanted to work on.<p>Often the Jedi Masters were tapped to teach intro engineering course to new engineers on the specifics of the type of projects this company worked on, so this was a quasi-academic and quasi-consulting gig for the best of the best engineers.<p>As a fairly new engineer, I got assigned to a new group and invited to a meeting that could impact the system I was working on. I show up and it is a meeting with an engineering partner (outside company) that was contesting some calcs regarding the pipe strength and mounting requirements for an installation (multi-billion dollar project). Their engineering team was insisting on assumptions that would have quadrupled the cost of a system that our group was responsible for, not to mention weeks or months of delays to recalc and redesign the system. Unbeknownst to me, this dispute had been at logger heads for months with no resolution.<p>One of the Jedi&#x27;s, let&#x27;s just call him Fred, taught me years before in the intro courses and I had remained in contact with him over time. Based on the courses Fred taught I thought he might have the expertise and interest in this area to take a look at this problem so I met with him and gave him the technical details. He agreed to attend the next meeting and advise but he made me do all the calcs, presentation and etc. for the next meeting but all under his guidance. So I go through my PPT presentation and at the end the other company&#x27;s engineers have all sorts of objections, disagreements, etc. So our Jedi steps in and starts fielding questions and asks them to justify their position. It turns out that their reference text they were using to justify their position was actually written by Fred! I can still hear the other engineer say, &quot;you mean you are Fred XYZ that wrote book ABC&quot; with awe and respect in his voice. It turns out they were missing some important exceptions and qualifications later in the book that Fred cited and the meeting and conflict was resolved.<p>So the moral of the story is to always have a Jedi in your corner? No.<p>The moral of the story is that engineers and problem solvers (and I assume coders) have different motivation than the &quot;success&quot; of big, showy career managing a lot of people. We (technical people) love to solve problems and management is projecting their values onto technical people when they offer them management positions as &quot;promotions&quot;.
评论 #8644725 未加载
评论 #8644773 未加载
JimboOmega超过 10 年前
Am I the only coder who&#x27;s always wanted to move into the business side eventually? I go back and forth on if I want to pursue an MBA every couple years or so (though I doubt the education would be worth it, it&#x27;d be a stamp on my resume for wanting to go that direction).<p>Working with brilliant people and managing people problems are very complex and interesting to me.
评论 #8644675 未加载
评论 #8644686 未加载
评论 #8644813 未加载
评论 #8646101 未加载
评论 #8644700 未加载
morgante超过 10 年前
A lot of people in this thread are pointing to the possibility of a technical track, but I just don&#x27;t buy it.<p>Any technical track stops far short of the management track, even in the most enlightened of companies. Taken to an extreme, you don&#x27;t get to be CEO off the technical track.<p>Ultimately, if you want more money and influence, you have to choose the management track. The technical track just exists to keep technical talent from leaving——look at any companies with technical tracks (ex. Facebook) and you won&#x27;t find their top earners on it.
评论 #8646160 未加载
评论 #8646349 未加载
评论 #8646267 未加载
评论 #8646253 未加载
fein超过 10 年前
For me its pretty simple:<p>Pay me what I&#x27;m worth. None of this managerial shite, just dollars. I will be happy.
评论 #8645420 未加载
评论 #8644868 未加载
评论 #8644662 未加载
评论 #8644539 未加载
评论 #8644548 未加载
chuckcode超过 10 年前
I really like the idea of &quot;handoffs&quot; that the article discusses It indirectly brings up what I see as a major problem for some of the most talented engineers I&#x27;ve worked with which is that some point they get too bogged down with the incremental features and maintenance on all the amazing stuff they&#x27;ve done in the past to work on new things. When it would take them a couple days to implement&#x2F;fix X but weeks for someone else to come up to speed management just can&#x27;t resist assigning it to them and eventually they become burnt out. Code reviews and mentoring can help this to reduce the time for new folks to spin up and contribute but I think a formal notion of handoffs is a really interesting idea.<p>Having been both an engineer and a manager, yes different tracks for different people are really helpful. The main thing I&#x27;ve learned is that different people want different rewards an there is no substitute for spending the time with people to figure out what sparks joy for them. Usually there is some baseline of money but often freedom, respect, and cool projects are just as important.
icyfenix超过 10 年前
Well yeah on the dollars++ and the equity++ - often that&#x27;s a harder sell, existing managers usually have to have some kind of thing to point at in order to make those things manifest - a lot of non-coders don&#x27;t know how to quantify your contributions- these strategies are supposed to add up to raises, promotions, bonuses, etc., and make getting the tangibles you want easier. Plus, if the tangibles don&#x27;t come with the thought leadership recognition, someone else will usually come along, and recognize you in the way you want to be recognized.
azimuth11超过 10 年前
Thanks for this, it helped me think through some very specific things that I have been struggling with at my startup. I joined out of school as one of the first engineers excited as hell, but have been somewhat sad&#x2F;depressed&#x2F;etc. over the last few months because I&#x27;ve felt a lack of direction and proper guidance.<p>Over lunch, president asks me if I wanted to become an engineering manager or something of that nature as well as take management coaching classes. It was a very sad thing to hear someone say to an engineer.<p>We want to lead by example. Thought, learning, and then code. We want to set or be a part of an engineering culture that has the freedom to be creative in our space. Some roles that jump out at are the developer advocate type roles. Not just &quot;Hey, look at what you can do with our APIs&quot;, but be learning and sharing that knowledge with our peers and others around the web (recruiting).<p>Maybe it&#x27;s time for a change.
评论 #8644583 未加载
Whitespace超过 10 年前
Having just become a co-manager for ~50 engineers, this is really interesting and timely advice. I don&#x27;t pretend to have all the answers about how to reward great engineers, so hearing more people speak about this is really useful to me.<p>My initial reaction is &quot;reward them with more things they can say no to&quot; but that ends up being project management-y if not outright manager-y. I&#x27;m very curious to hear more specific examples where this isn&#x27;t the case.<p>If anyone in NYC and is in a similar situation to me, I&#x27;d love to meet up for coffee to share notes. Or in SF, for that matter (I&#x27;m here about once a month). Email in my profile.
smenko超过 10 年前
Err... Money???<p>Most people will (rightfully) settle for money. Because people need love, and to demonstrate love you need to show that you care, that you&#x27;re willing to give something up in a hard situation. And the only thing a company cares for is money. So, I want said company to give me money. More money than the &#x27;manager&#x27;. Because I can do their job just as badly as they are doing it, but they can&#x27;t do mine at all.<p>I don&#x27;t want your stupid titles and shit - those are cheap. Cash is what will hurt you. Pay up if you care!<p>And when people realise they have to pay you or lose you, then you get respect. Priceless!!!
jaunkst超过 10 年前
Give me equity stake. I don&#x27;t want to manage, I want to come out of the end ready to start my own venture or retire and do what I love and build and awesome open source project to give back to the community.
评论 #8644804 未加载
Bahamut超过 10 年前
I think the most important thing is to have a conversation with your employees - ask them what do they want to do, and how do they want their career to evolve. Constantly keep in sync with your employees&#x27; desires, and you should be fine.
gvb超过 10 年前
My summary&#x2F;option: Technical leaders should be front-running the team so that, when less experienced engineers run into problems, the technical leader knows in what direction to point the team to find the solution to the problem.<p>Having technical leaders stuck on legacy Sisyphean tasks (a) sucks up the time that should be used front-running the team for solutions to future problems and (b) removes opportunities for less experienced engineers to learn new ideas and skills, hindering their education and development.
atlantic超过 10 年前
I worked for a while with a software consultancy, as a .NET consultant. One of the nicest things about the company what that they had two distinct career paths for developers - one technical, the other in project management - and they asked us up front what our preference was, and directed our work accordingly. I always thought other companies could take a leaf from their book in this respect.
ZenoArrow超过 10 年前
Perhaps more companies would benefit research teams, who work on the next generation of products with less management interference. Being promoted to the research team could be a useful incentive to keeping talented engineers around. If they do stick around, the maintenance team could still consult the research team about the previous system they built.
luckydude超过 10 年前
It&#x27;s late so I&#x27;m going to screw this up but there are coders and there are leaders. The leaders think about other people and how to make those other people be successful. The coders are more about themselves. Which is fine, I&#x27;d just look for people who are trying to make other people be awesome.
clueless123超过 10 年前
If a sales guy sells 10x, he gets 10x commision.. If a coder produces 10x, pay him 10x.<p>What is so hard to understand about that ?
评论 #8644618 未加载
评论 #8644757 未加载
评论 #8644615 未加载
评论 #8644613 未加载
评论 #8644803 未加载
评论 #8651861 未加载
评论 #8644625 未加载
firebones超过 10 年前
Compensation, equity and when those are ultimately satisfactory, autonomy.
icedchai超过 10 年前
My experience has been that most managers wind up going to meetings all day and stop contributing technically.<p>I briefly (a couple years) managed a small team (&lt;5 developers) and it was torture. Not worth the relatively small increase in $.<p>How do you reward your skilled coders? Let them do real, interesting work and not deal with bullshit (this includes all the time wasting &quot;agile&quot; meetings.)
vinceguidry超过 10 年前
As a coder that&#x27;s soon to be taking on a management responsibility, I definitely feel the weight of it, but I&#x27;m up for the task of figuring out leadership. I might well be more suited to it than a lot of engineers would, but I also think that management and leadership is less hard than it seems and that engineers would actually be better at it than their superiors if they would just give themselves a chance.<p>The trick to it is to realize that it&#x27;s not, actually, a skill, when you break it down. It&#x27;s an opportunity to structure part of the operation of the company the way you want to structure it. You can take all those ideas you have about how to run the company better and put them into practice on a small scale. You do not have to give up engineering, you&#x27;re just also engineering at a bigger level than just with machines. You can and should still program, and still avoid pointless meetings by bringing your laptop to them and working through them.<p>You&#x27;re engineering human systems now too. There&#x27;s no conflict with the other machine-type engineering, because the two are intended to work in concert. So don&#x27;t create one where it didn&#x27;t before exist. Humans are easier to engineer than machines in many ways. You can tell a human to do what you mean, humans are smart and machines are stupid, a machine will only do what you tell it to do. You can&#x27;t tell a machine to exercise judgment or grant them power or flexibility, they wouldn&#x27;t know what to do with it. But grant flexibility to a human and he&#x27;ll make your job much much easier.<p>Power necessarily involves freedom and flexibility, if you&#x27;ve an expectation to meet a responsibility without giving yourself the latitude to meet that expectation your own way, including the willingness to put your foot down to ensure your turf is protected, then you are putting yourself through hell. It&#x27;s simple, decide what you need to get the job done, then acquire the resources, then follow through. If the expectation is unreasonable, then change the expectation. It&#x27;s not hard, all you have to do is explain to people that it&#x27;s unreasonable and offer an alternative. As an engineer, you should have already learned the skill of dazzling people with techno-babble. As a manager, they have to take your arguments seriously and compromise with you. You can&#x27;t promote someone to management and then proceed to ignore their opinions. That&#x27;s the whole point of the promotion.<p>I go home after eight hours. My boss will put in ten hour days but I won&#x27;t volunteer to. I fully expect my new report will go home after eight like I do. When I wanted to move to flex time I just started coming in later and when my boss noticed, I just said I was going to choose my hours from here on out. My boss insulated me from office politics until I was ready to deal with it and I will extend the same protection to the new guy. I was somewhat worried that the promotion would come with strings attached. If anything they&#x27;re more worried that I&#x27;ll get cold feet than they are that I won&#x27;t measure up. So they&#x27;ve been kissing my ass extra hard lately.
评论 #8644977 未加载
评论 #8645039 未加载
known超过 10 年前
Pay his taxes
girldevninja超过 10 年前
Great article!
icyfenix超过 10 年前
Ah sweet, thanks for the share. I hope this helps engineers do things that make them happy.