News for hackers. Stuff that matters.
Re:What I Wish I Knew When Starting Out as a Software Develo... by michaelochurch on Monday January 26, 2015 @12:39PM (#8948316)
Pardon me for this, but I'm a bit irked by being taken out of context.

Most obviously, Michael urges young programmers deciding how much effort to put into their work to "ebb towards underperformance".

That's not what I said. From the source (on Quora, here: http://www.quora.com/What-do-software-developers-age-30-and-...):

3. Recognize underperformance and overperformance and avoid them. There are a lot of low-effort players who stay employed for years. This isn't a bad strategy if you're settled, but I wouldn't fall too low. That said, the only people who typically get fired for underperformance are the people who fail so badly that they generate work for others. People who hide and do little tend not to make any enemies. At the same time, be cautious of overperformance. This isn't like college where challenging your professor's ideas could earn you an 'A' if you argued your point well. Overperformers often also generate extra work for their superiors and colleagues and draw unwanted attention (see: McNulty in The Wire) and are more likely to be culled for "performance" (98 percent of "performance management" in companies is politics) than underperformers. I'm not saying that you shouldn't work hard and do a good job and learn as much as you can. That's not necessarily overperformance. In my experience, though, overperformance is much more dangerous than underperformance. It can get you just as fired and it will happen a lot faster. If you end up stuck between the two, prefer underperformance.

I'm not saying that people shouldn't work hard or do a good job. On the contrary, I think young people should bust their asses at growing the skills and contacts that will serve them well for the rest of their lives. I'm saying "avoid overperformance", and overperformance isn't the same thing as "doing a great job". I'm saying, "don't become like McNulty on The Wire" (or a certain person at Google who tried to prevent a product failure and got burned for it). McNulty is a textbook overperformer: he loves the job, it doesn't love him back, and he puts so much into it that it destroys his life and career.

Sorry, but I'm pretty fucking pissed out this being out there like that. That was way the fuck out of context. I wasn't happy with the Lifehacker edit either but I didn't speak up about that because I didn't see it as a big deal. But I am definitely not telling a generation of people to slack off at their jobs.

Re:What I Wish I Knew When Starting Out as a Software Develo... by matt_s on Monday January 26, 2015 @01:00PM (#8948442)
Your article can be reinforced by the Ribbon Farm analysis of "The Office" [1]. What you have stated about over-performance seems to line up nicely with the "clueless" in that hierarchy.

To quote from Ribbon Farm article: "The simple reason is that if you over-perform at the Loser level, it is clear that you are an idiot. You’ve already made a bad bargain, and now you’re delivering more value than you need to, making your bargain even worse. Unless you very quickly demonstrate that you know your own value by successfully negotiating more money and/or power, you are marked out as an exploitable clueless Loser. "

[1] http://www.ribbonfarm.com/2009/10/07/the-gervais-principle-o...

Re:What I Wish I Knew When Starting Out as a Software Develo... by dpritchett on Monday January 26, 2015 @02:52PM (#8949161)
Michael has written nearly 30 essays on the Gervais Principle - check out his blog.
Re:What I Wish I Knew When Starting Out as a Software Develo... by matt_s on Monday January 26, 2015 @03:37PM (#8949414)
I will have to check them out and possibly emotionally prepare myself since living through seeing this in a large company is hilarious and sad at the same time.
Re:What I Wish I Knew When Starting Out as a Software Develo... by marktangotango on Monday January 26, 2015 @01:33PM (#8948649)
>>I'm saying "avoid overperformance", and overperformance isn't the same thing as "doing a great job"

Can someone explain this formulation of 'performance' without referencing "the Wire"? Ie is it simply long hours? Or is it long hours coupled with getting a lot done, in a good way? Or is it getting a lot done, and breaking things for everyone else? Or ...?

Re:What I Wish I Knew When Starting Out as a Software Develo... by sheepmullet on Monday January 26, 2015 @10:02PM (#8951025)
Basically going outside of the, often implicit, boundaries of your role.

For example if you are a developer and realise your project needs to engage another team NOW for a critical deliverable due in 3 months and you spend your time on this task then you run the serious risk of pissing off both your manager and the project manager.

Or for example putting together a prototype that shows how another teams work could be automated.

Or pointing out flaws/discrepancies of a high profile product. Or telling a senior manager how a project is really doing, etc.

The bottom line doesn't matter as much in terms of respect and career progress as it should. There is a misconception that you can get away from politics if you work for startups or smaller firms but that's just not the case.

Re:What I Wish I Knew When Starting Out as a Software Develo... by michaelochurch on Monday January 26, 2015 @11:02PM (#8951170)
You nailed it. My upvote is not enough, and you will probably get fewer than you deserve for this post.
Re:What I Wish I Knew When Starting Out as a Software Develo... by cadlin on Monday January 26, 2015 @02:02PM (#8948837)
It's more like getting a lot done and breaking things for everyone else. Imagine your boss has a terribly, horrendously stupid way he wants things done. Overperformance would be going over his head to his boss to try to change the awful policy. It might be the right thing to do, but you're only going to piss off your boss in the process. Michael is saying it's better to do what the boss asks in that case, but only do the minimal amount of work necessary, instead of going off on a crusade that will only cause trouble for yourself and provides no benefit.
Re:What I Wish I Knew When Starting Out as a Software Develo... by kpapke on Monday January 26, 2015 @02:33PM (#8949028)
At my first job, I used to grind out work, staying hours past when most people went home. For me, this was the best time to actually get work done without the distractions. But I remember my project manager, who was twice my age, getting pissed off at me and telling me to go home. When I was completing tasks and sending off emails, I was just giving her more work to do that night. So that would be overperforming I think.
Re:What I Wish I Knew When Starting Out as a Software Develo... by hobs on Monday January 26, 2015 @12:47PM (#8948348)
Don't worry, only someone purposefully attempting to misunderstand you would take their interpretation as the context.

As a previous overperfomer(who got burned for it) I find overperforming is often a product of misunderstanding what the company wants you to do, and in the end it doesn't help you, your peers, or anyone except your personal idea of what you think is right, without regard to reality.

Re:What I Wish I Knew When Starting Out as a Software Develo... by mgertner on Monday January 26, 2015 @02:44PM (#8949097)
Author here. I linked to your post and there are comments on the blog (which you took advantage of). No need to be pissed off. I still disagree with this particular point (and I'm not sure why you say I took that quote out of context), despite your clarification. But overall I think you provide a lot of good and valuable advice that might be counterintuitive to younger devs entering the corporate world.