Earlier quoted context omitted.
In my experience, people are usually promoted into management when they demonstrate leadership. I see you talk about your technical ability a lot, but that is generally not the core competency of an engineering manager. I suggest working on those abilities. It is very much so one of those situations where doing the job will get you the title.
> In my experience, people are usually promoted into management when they demonstrate leadership. Really? In my experience, people are often promoted into management when they demonstrate political ability. Often the people who I consider the true leaders - engineers who everyone considers competent, good advisors, mentors and role models, etc - continue quietly being engineers. Several times, I’ve seen organizations…
Why Good Developers Are Promoted into Unhappiness (2007)
211–220 of 235 posts
Re: Why Good Developers Are Promoted into Unhappiness (2007)
#212Earlier quoted context omitted.
Then what is the point? Are you just there to gather your paycheck? I mean, to an extend, yes. But you need to be able to excert some positive effect.
big companies do not innovate. (counter examples welcome!) unless you’re in a 1-20 person startup, your impact is -5% to +5% as a division. Essentially you’re stroking egos: yours or management’s. best to choose the latter and try your hand at changing the world in after-work projects.
That new smell for dove soap. The thicker papertowl bounce came out with are all examples of innovations.
Changing the world.. that's a dangerous idea companies want no part of.
Re: Why Good Developers Are Promoted into Unhappiness (2007)
#213I wrote code like a madman and then went into management. I like management, but I understand what the author of this article was getting at. I had an identity crisis early on doing management. I liked to tell people what to do, because I had a big map in my head of where things should go. Because of this developers sort of organically gravitated to me for guidance even before I had the official job. However, I also…
So how DO you deal with people under you writing code under you that just boils your blood? Especially if you instinctually see that their contributions are always more counterproductive than not, but everyone else (including their people manager) thinks they're alright?
Get to the point where you can convey the underlying reasons for them: why is it important to you? What’s going to be worse or slower with their solution? What future problems is your solution avoiding? How can they identify similar situations and apply the same concept next time?
It is good that you see these things instinctually as you say but if others don’t (including the coder in question) then you can make improvements by conveying this to them. And that is frequently more than half the battle in getting improvements operationalized: getting others to adopt and push and spread your good ideas as their own.
In a healthy org, these developers should be open and eager to listen, learn from new ideas, and adopt improved methods or outlooks, especially from a tech lead (or equivalent), who in turn should be able to update his/her own methods/outlooks when similarly presented with improvements.
Re: Why Good Developers Are Promoted into Unhappiness (2007)
#214I believe IBM was the originator of this approach, but could be wrong.
Re: Why Good Developers Are Promoted into Unhappiness (2007)
#215I wrote code like a madman and then went into management. I like management, but I understand what the author of this article was getting at. I had an identity crisis early on doing management. I liked to tell people what to do, because I had a big map in my head of where things should go. Because of this developers sort of organically gravitated to me for guidance even before I had the official job. However, I also…
So how DO you deal with people under you writing code under you that just boils your blood? Especially if you instinctually see that their contributions are always more counterproductive than not, but everyone else (including their people manager) thinks they're alright?
I haven't dealt with people under me who write truly abysmal code so far, mostly because I am a picky hirer, but that subpar code that my people have written is my fault, because it's my responsibility to make them better programmers.
Re: Why Good Developers Are Promoted into Unhappiness (2007)
#216Earlier quoted context omitted.
It's _vastly_ harder to get ahead on the "engineering" track. At Google, for instance, it's to the point where as a manager you barely need to have a pulse to get promoted (as long as your reports are any good), whereas on the technical ladder promotions to Staff level and above are stupid hard and downright nondeterministic. That's why many engineers there, who have little to no leadership skills or inclinations, en…
Google aside there is nothing worse than getting stuck at middle management in a software corp after 40 - 50. You are expensive, replacable and disposable.
Re: Why Good Developers Are Promoted into Unhappiness (2007)
#217For many developers, they turn out to be good at project management, its not much different conceptually than being an architect, this issue is, once you 'level up' you're expected to stay there, rather than moving back to develop for some period of time, and letting the next guy get tapped for project management - It think more companies rotated those roles around, they'd see greater retention, greater employee happ…
I don't know where you are from, but in my experience the roles are very different.
As an architect you have to provide technical guidance over a domain that you know like the back of your hand.
As a PM, you have to manage a project that straddles multiple domains, some of which are completely alien to you, and you are explicitly limited by the scope, deadlines and your budget.
As a PM, you have to trust (and goad) multiple experts if you want to get anywhere.
Re: Why Good Developers Are Promoted into Unhappiness (2007)
#218Earlier quoted context omitted.
Most of the companies I’ve worked for have utterly no possible capacity for formally managing special projects. It will either be an argument over what business goals the project must serve, whose autonomy gets to drive the project, politics about who gets to work on what. The only successful special projects I’ve ever seen are ones that are off the books initially, possibly even pissing off product managers or other…
I've done special projects at a large, somewhat stodgy company, and the general pattern was that you had about nine months to do good work, just engineering and business folks together, after which point the "project management office" would get their hooks into it, and any further scheduled meetings would be prevented from achieving anything productive in deference to the new project manager's interest in gantt char…
Re: Why Good Developers Are Promoted into Unhappiness (2007)
#219Earlier quoted context omitted.
Let me be crystal clear: I'm talking about building up a side business in your spare time. > If you are talking about starting a business on the side and working full time, that means you are sacrificing some combination of time with your family, exercise, and time that you could be putting in getting ahead at your current job or acquiring skills that would help you get a better paying job. You think you somehow lear…
That even lessens the chances by starting it on the “side”. You will be competing with people who are better funded and are able to commit to it full time. What are the chances that a “side business” is going to make $150K to 200K a year? On a side note, why are you so relentlessly negative? Most of the comments you've made in this thread are needlessly hostile, sarcastic and bitter. Did a side project touch you inap…
One side project doesn’t have to earn 200k/yr. you can have 5 of them, each making 50k. Running them as single software company is way less management work than managing your team in big company environment.
Re: Why Good Developers Are Promoted into Unhappiness (2007)
#220Earlier quoted context omitted.
How do you, as a contractor, find this sort of work?
From your network, and everybody has a network. However, you need to make sure that your network knows that you're available. So: email everyone you know (also non-programmers) a 4-sentence email that you're now a contractor. Explicitly list the domains and technologies you can "hit the ground running" at, and focus on those. People need to be able to see you as "a great Java programmer" or "a great iOS programmer".…
Would you then use a recruiter or something like that? I don’t think I would get any gigs using my network.