10 ms·
Habits of Highly Overrated People (2013)
- paulpauper 4y agoReminds me of crypto. Overhyped and underdelivers.
- safaa2000 4y agoMinutia is the definitely the bikeshedding holy grail of business theater.
- brazzy 4y agoThat's because getting lost in minutiae happens to nearly everyone, even most people who are competent and hard-working. Avoiding it is a skill not many are very good at.
- enkid 4y agoThe problem is there are times when minutiae is important. The skill is knowing when it is important and when it isn't.
- revskill 4y agoWhy that is the matter ? The problem is in bad project management, technical leading and outcome management instead. Solve those issues first, and there will be no overrated people.
- tyroh 4y agoThis is precisely what's happened in our company. The project management head was not a servant leader and actively avoided doing real work while telling others what to do and promising to do things that never happened. Sadly, this person is still with our company at the time of this writing, but thankfully not anymore in a role where they can derail work. What really struck a nerve in me was that I had to catch all the work this person wasn't doing, and I only realized it after I got burned out from all the extra work. The bigger issue then is that you can't solve this because often, the person does a good job of hiding the bigger issue by deflecting to smaller, more pressing ones.
- ilyt 4y agoThe worst case of that took 2 other managers with him. He was kicked but project was so mismanaged that the next 2 PMs outright fucking left, with last one throwing comment like "well, they told me that they will be throwing me on deep water but they didn't tell me it will be with concrete boots on!". To be entirely fair fuckup wasn't totally his (the person involved in selling it to customer sold Perl based piece of software that we only had to "lightly customize", that turned out to be a lie and we had no Perl devs on staff, so it turned into some monster...) but still.
- draw_down 4y ago
- 300bps 4y agoFound myself simultaneously laughing and being horrified by identifying techniques used by people I've worked with. The advice at the end is spot on. It also turned out that the best way to appear generous was actually to be generous since false displays of generosity were usually discovered and resulted in ostracism I'll help anyone out at work. I'll teach anyone anything I know. I will never throw someone else under the bus. I'll take credit with "we" and blame with "I". I've been rewarded for this behavior at the places I've worked at.
- gpderetta 4y agoFWIW, have had the same experience.
- tomger 4y agoSame. Long term vs short term.
- qsort 4y agoThe best mix is a lot of genuine collaboration with a tiny bit of backstabbing occasionally thrown in. Be genuinely useful, cooperative and valuable, that's a given. It speaks for itself, it's rewarding to you personally, and it's the only way to do not burn out. But don't be afraid to play hardball. Don't cover for incompetence. Don't be taken advantage of. Don't be a sucker. The simple wisdom of tit-for-tat is what I recommend.
- genghisjahn 4y agoThese articles come out with some regularity, and yet no one ever says, "Yep! That's totally me! I'm a non contributing zero but I've made a living at making others think I add to the team!" Everyone knows people like this, but no one is one.
- theknocker 4y ago
- drbeast 4y agoWell, that's actually me. I do a lot of stuff on this list. No shame, I'm in upper management.
- davesque 4y agoI think the reality is that anyone might engage in these behaviors from time to time. I've seen myself doing some of these things in my weaker moments and I've seen others doing them. And I've seen those same people turn around and contribute positively on other days. Of course no one is going to categorize themselves as highly overrated. Maybe that's because people often don't reliably fit into specific categories.
- ilyt 4y agoWell, some of them are not exactly something you'd do on purpose, can be just from the work flow, or just how some people are > Distract with Arguments about Minutiae is easy for tech people as we could discuss every detail for tens of minutes ignoring the fact remaining 4 people in the meeting don't give a shit about the minutia of solution, just that it is done > Time It So You Look Good (Or Everyone Else Looks Bad) is easy if you (or your manager!) mismanages priorities of tasks and you don't have habit of starting with stuff that might block other people first.. Like, simeple example, ticket looks "long" from title so you don't even read it before you have longer time period. You read it, then it turns out before start you need some information first from the submitter. You now delayed tasks by hours, maybe days, compared to if you read it first, sent the "give me stuff I need" message, then went back to doing other things before the response came
- jiggawatts 4y agoI get the strong impression that many (most?) of the people fired from Twitter are just like the overrated person described in the article. People love to act like Elon is some sort of mouth-breathing man child who stumbled into the CEO position through nothing but luck and connections. Meanwhile, if I was to take over a company that's made up of thousands of developers, the first thing I would ask for is examples of the code written by those developers. Don't tell me how fantastic and important you are. Show me the commits!
- JustLurking2022 4y agoI might believe that to some extent except that not all development jobs lend themselves equally to cranking out commits. Sure, if you're working on a well defined feature with all dependencies already built, you can really crank stuff out. However, those also tend to be the easiest jobs filled by junior developers. Solving the less well understood/defined problems often generated fewer commits per day but often generates more value.
- RC_ITR 4y agoI get the strong impression that you‘ve never led a multi-billion dollar organization. Don’t show me the random code you built that makes a users like history load 500 milliseconds faster, talk to me about how to make the product better/more engaging/monetized!
- q-big 4y ago> Don’t show me the random code you built that makes a users like history load 500 milliseconds faster, talk to me about how to make the product better/more engaging/monetized! Honestly, if I were the CEO, I would ask for the former if I were looking for the good programmers to keep since these are the things that make the technological base of the company run. The answer is of course likely different if I were looking for the managers to keep ...
- RC_ITR 4y agoI mean, again, $44bn is on the line here and 'well functioning app' is not why things are worth that much (what share of YC's value is Hacker News for example?). Companies release financial statements for a reason.
- doctor_eval 4y agoYou’ve pretty much described the narcissist who headed a company I worked for a while ago. Example real life interaction: Me: please can we defer this non critical meeting until after product launches in a few weeks as my team is super busy and we are about to sign a customer. Them: Non critical meeting is important for team building, which is more important than product, and must therefore go ahead. Me: ?????? It was nice to read this article and finally have a place to put all my WTFs.
- ilikeitdark 4y agoElon Musk
- LAC-Tech 4y agoFires most of the work force and the site is more pleasant than it was in 2020? Sounds like the opposite of Elon Musk.
- croes 4y agoMore fake check marks, totally pleasant.
- k8t 4y agoHe's the CEO and a huge voting share owner of his companies, why would he need to pretend to be working? Also, it's probably hard to make breakthroughs in space travel and electric vehicles doing fake work. There's been a huge amount of leaks, rumors, and reports about Elon from within and from without his companies. He's been accused of a lot of things, but fake working has not been one of them.
- croes 4y agoThe breakthroughs were done by his employees not Musk or do you praise Pope Julius II. for the Sistine chapel ceiling? BTW were is the breakthrough in Teslas?
- musingsole 4y ago> BTW were is the breakthrough in Teslas You're either uninformed or being pointedly obtuse. Tesla has a massive patent portfolio -- starting with the roadster's gearless transmission. It's a point of fact that building a massive car company within a crystallized industry was a breakthrough in its own right.
- croes 4y agoPatents != Breakthroughs
- neilv 4y agoSome of the symptoms the article gave are painful to read, because that can also be what it looks like when a person is blocked outside of their control (e.g., another team not delivering, or up the chain has a problem), and trying to fix it. Before trying to assign individual blame to a part, try to debug the actual system problems in team and organization.
- pdonis 4y ago> that can also be what it looks like when a person is blocked outside of their control (e.g., another team not delivering, or up the chain has a problem), and trying to fix it Near the end of the article there is a good antidote to this: "These things are a whole lot more transparent than the people who do them think they are" Yes, if you just look at one incident in isolation, it might be difficult to distinguish "productive but blocked outside of their control" from "unproductive but trying to obfuscate that". But over time, the difference will be clear to everyone in the organization who actually matters.
- srcreigh 4y agoThat’s not a good antidote. Some systemic problems don’t get fixed and consistently cause problems. They aren’t always explicable to a wide audience either. A good antidote is giving frank feedback and working together to come up with a solution.
- pdonis 4y ago> Some systemic problems don’t get fixed and consistently cause problems. That's true, but if you're in an organization like that, the fact that some people are unproductive but use the methods described in the article to obfuscate that fact is the least of your problems. Your real problem is that your valid warnings about systemic problems aren't being listened to. Often the only way to fix that problem for yourself is to change jobs. > A good antidote is giving frank feedback and working together to come up with a solution. If you're in an organization where this can work, you're in an organization where the people who matter can tell who is actually being productive and who is not, and aren't fooled by the tricks described in this article. Which means that those tricks actually aren't a problem that is worth worrying about, which is why I gave the observation I just described as an antidote.
- pojzon 4y agoWhen I spot ppl like that driving the company towards bottom I know its time to jump the ship. Over 10 years of work, jumped few times like that. Each and every time the company went to bin. Following those kind of ppl does not work, having too many of the also. But its very hard to push them out once they made “connections” and “politics” going.
- levelforge 4y agoThis is so frustratingly true… I’ve seen this play out over and over… often these people are mistakenly promoted and eventually they sink the ship.
- mberning 4y agoMan the slackware clock thing is so common. “Is that in confluence?” burns me up regularly. Things like how to delete a file in git. Or revert a file. As the number of tools required to build software continues to grow there are more and more opportunities for people to play dumb and act dopey.
- renewiltord 4y agoI don't see how that can work. If someone does that even once you're going to lose respect for them. Twice and you're going to fire them for just not being smart enough.
- mberning 4y agoIn a sufficiently large organization with legal, hr, compliance, etc. it can be brutal to get someone fired for incompetence. Often they will start looking at the manager rather than the employee. Especially if you inherit a whole team of these folks and want to purge. Sadly it is often easier to just spoon feed these types of people than get them fired.
- dilyevsky 4y agoThis was an extreme example, there are many more subtle variants of this usually complaining about devenv or some other tooling. Here’s one making front page recently: https://daniel.do/article/laying-myself-off-from-amazon/ https://daniel.do/article/laying-myself-off-from-amazon/ And hey sometimes they have a valid point but yeah usually they will feel out management about it and if it works you’re going to hear about it non-stop
- srcreigh 4y agoThere’s a very fine line. What is the standard way to set up the editor? How do people connect to databases? How do people generally reproduce an issue? What’s the attitude towards prod DBs? In fact, what is the expectations around asking questions? Each of these questions has many different answers. Even a very experienced developer may never have seen other options and have intense expectations but not write them down because they’re “obvious”. I wouldn’t be surprised if some company had some standard way to do certain Git operations due to some possibly misguided internal tooling effort… etc If you really don’t want people to ask questions like that, you need to have company specific documentation which is required reading.
- furyofantares 4y agoIn the environments I've been in, it feels like all of these things would set off everybody's BS detectors extremely quickly
- token8791 4y agoI did some of these things and I slowly getting over them, thanks to some very generous colleagues who can overlook my downsides. To be honest, some of these problems are less the problem of an individual but the environment - where we constantly have to or we want to point out the value that we provide. Some things are even more painful, and I'm glad I'm recovering from them, like over-communicating. Some people have so little to provide in terms of value that talking becomes the main output - and that usually slows down projects. I'm also recovering from being bossy after having worked with managers who were basically never bossy at all - it's such an important trait, yet relatively rare.
- didibus 4y agoTo be honest, I don't often encounter this behavior in developers. In more management or leadership position, you can see it though. Developers have concrete tasks to work on, what I often see is simply some of them can't really figure out how to complete the task if it's not layed out to them in every detail, and they can be very inefficient at overcoming any problem along the way. The example of the developer stuck because of the clock is a good one. From my experience, this person isn't faking work, they really are stuck due to this problem and can't make decisions as to how to get past it, and don't know how to proceed. Knowing that the clock doesn't matter and they can safely ignore it for example, is not something they know, or in this case, why it's wrong and how to fix it, they might also not know. They're stuck because they have no clue how to figure it out and need help. Ya, it also means they're not as good as another developer that has a much deeper understanding and knows all this, but I wouldn't call a less knowledgeable or less talentented developer someone that's pretending to work or overrated. Now you do have the kind of developer that's all talk, no walk. They are the ones that similarly don't know how to do things, or do things well, but they're very confident none the less, criticize others, and always talk as if they know and they're awesome. Again though, I feel these developers everyone knows that they're all talk no walk, because other devs can see the kind of code they wrote or don't, what their real output is, etc. That said, to management sometimes it might not be as obvious. But where things get real tricky is in management or leadership roles. Because in those positions, your job is to simply make decisions and guide others. But since you don't actually produce work, if you actually don't make any decisions, and actually don't help guide others in any valuable way, but still appear to be, the people actually doing the work will still have to figure out what to do and decide how to do it. And it becomes very easy to take the credit from them, as you were the "leader" or "manager". And even when you're good at making the right decisions for the project or team, or company, and are good at guiding others, it's very hard to measure how much you contributed truly, what would have happened if you hadn't for example, it's almost impossible to know. In those positions, it becomes almost about how well you can market that you did in fact have influence and were critical to success. And this is true even if you are really good, because it will be very hard for others to assess your real impact, so if you can't market it to them and make them know it, being good won't be enough. It's a tricky situation, but it means that leaders and managers, both good and bad, will all be doing some form of what this article talks about, since they have too. Another challenge in those roles, is that the impact of a single decision can be huge, but then for months you might not have to make any other decisions, and so you need to appear "busy" none the less. For example, choosing what is the next project the team will pick up, or that a new service will be created to deliver on X. Thats just one decision, but it's a huge decision, the impact of that choice is dramatic. Yet maybe you spent 2 months thinking about it, then took the decision, in that 2 months, you showed no sign of work, you were just thinking about what's the best way to proceed. And after having made the decision, there might be months where that's it, you've got nothing else to do but wait on other people to design and implement the new service X, or to deliver on project Z. Again, what do you do in the meantime? How do you not appear like you're no longer useful?
- throw-self-away 4y ago> Seriously. These things are a whole lot more transparent than the people who do them think they are Has anyone seen articles on how to effectively manage/coach people with these habits? Extrinsic motivation tactics tend not to work, and appeals to intrinsic motivators are often met hard with #6 and #7.
- H8crilA 4y ago> Managing unmotivated people is hard, so don't. A quote I've seen in an article on management.
- rramadass 4y agoThere are plenty of articles out there, see for example; HBR's 10 must read series, On Communication, On Managing People and On Managing Yourself (2-vols each). You might also find Edward Deci's Why We Do What We Do: Understanding Self-Motivation useful. But ultimately everything comes down to Responsibilities and Accountabilities with Definite Rewards/Consequences.
- lamontcg 4y agoDefinitely had a boss who was #2, #3, #4 and #7 and was more of a "Thoughtleadering Principle Engineer" rather than actual Manager.
- LAC-Tech 4y agoDaedtech is a highly underrated blogger. Strongly recommend sifting through his articles.
- frogpelt 4y agoOff-topic but this article describes pretty much all politicians.
- mruniverse 4y agoThe larger the company is, the better this works. Who knows what everyone really does? It's only the direct peers that will give side glances. And even then, it's risky. You can be seen as having sour grapes, not being a team player, etc. And everyone's busy with their own work as is. Why bother trying to call someone out? Large companies run on apathy.
- deterministic 4y agoWhat a great read. And so true. I have worked with people who exhibited some or all of those behaviours. Mostly clueless middle managers who only survived because of their ability to BS upper management and because of the ability of the team to effectively manage them and counter their incompetency.
- Octokiddie 4y agoA lot of people mistake activity for productivity, and you can capitalize on that. If you send one or two emails a day, summarizing what’s going on with a project in excruciating detail, people will start to think of you as that vaguely annoying person who has his fingers on the pulse all of the time. This is an even better strategy if you make the rounds, calling and talking to people to get status updates as to what they’re doing before sending an email. That word "people" is doing a lot of lifting. Some people will actually value behaviors like over-communication and other won't. It all comes down to culture. Organizations whose management ranks have a lot of over communicating, bossy, self-promoting, nit-picking, blame-pushing, excuse-spinning, credit-grabbers will promote the same kinds of people to top positions. But people who actually do the work will see right through these behaviors for the obvious plays for promotion that they are.
- slfnflctd 4y agoThis kind of behavior will likely make any normal person more stressed out and miserable than most actual work. You'll hate yourself. I agree with the author's advice at the end. I did it to a small extent while working for a large org where I was not under much pressure to produce or build up my skills, and it was a very unhappy time. Part of it was due to unresolved mental issues, part because I noticed others doing the same things, but regardless I have no desire to repeat the experience.
- RajT88 4y agoI know devs who practice bits of this to pad their credibility. They are good developers. So it is supplemental, not their main bread and butter. For sure it is intentional.
- austin-cheney 4y agoSounds like my previous employer. Almost nobody did any real work. There were meetings all day where a few people with complex accents talked over each other just to hear the sound of their voice while many people pretended to participate. Nobody wrote anything down. I really think people put so much effort into posturing that they could not write at the necessary professional level. I was completely upfront about how little work I did to everyone I talked to. Now I work for a small company with excellent leadership where I actually do real work all day.
- Existenceblinks 4y ago> If you’re currently doing them, stop. Hmm, I'm definitely not this kind of people .. but sadly the market rewards these people GREATLY. Most of rich dudes I know are exactly this kind of people.
- kuharich 4y agoPast comments: https://news.ycombinator.com/item?id=6965295 https://news.ycombinator.com/item?id=6965295
- satisfice 4y agoMost of the items here are good things that are taken too far. You can almost automate writing an article like this: take any set good things (writing code, releasing products, innovating, being kind to others, helping old ladies cross the street, etc.), take them to an unhelpful extreme, and say “don’t be like that.” Don’t obsessively add code, or release useless products for the sake of releasing, or reinvent things that are perfectly good and not worth improving, or be creepy like Dr. Jekyll, or stalk old ladies. I like people who keep track of status and make documentation, thank you! They are useful people! All you need to not overrate someone is to be a critical thinker who pays attention over time to how things are done.
- jacksonkmarley 4y agoPersonally I don't have much experience with people behaving like this, motivated by straight-up laziness or covering up incompetence so blatantly. These seem like they would be very obvious problem behaviours, and not as damaging as other more common but perhaps less overtly dishonest habits of overrated people. I have encountered many people who behave in harmful ways according to personal or organisational incentives that they or others could argue were legitimate. Technical people promoted above their managerial competence level for example, can end up being rated highly by upper management as they are seen to be experts, but can then go on to make terrible strategic decisions. Also non-technical project management professionals, using techniques that could be interpreted as legitimate, can be rated highly despite contributing next to nothing. Asking tech contributors for deadline estimates, recording the answers, and then chasing the overruns can seem like constructive action. Then you realise that there are no high level plans coming back that integrate the timelines in a constructive way, it's just a way to apply psychological pressure by getting investment in a target that can be held over people's heads.
- jongjong 4y agoThis article makes an interesting point but IMO it highlights 2 phenomema, not 1. The first phenomenon is that some people seem to be more talented and useful than they are while they are present within the organization. The second phenomenon is that when people leave an organization, their talents may be immediately discarded; they often end up being used as a scapegoats for any problem which remaining employees may notice after the person has left (possibly completely unrelated to the person). People tend to over-rate people who are present and over-demonize people who are absent. The demonization probably falls harder on people who were overrated (since it's backed by truth) but it can also fall on people who were genuinely talented and valuable - It depends on what kind of people remain in the company and what narrative serves the interest of those who remain.
- djmips 4y agoPerhaps a side note - but I know a case where someone whose code had a lot of bugs and design problems but when they were with the company they worked very hard and would address problems - often with band-aid solutions but at least they took care of their own messes so it didn't fall onto others. All of this hard work and long hours and diligence made them seem to management as if they were amazing. However after they have left, they are obviously no longer supporting their terrible code and the ones who had to take it over will certainly demonize the departed - it's a bit unfair but someone who isn't helping fix their own mess (even if they have a good reason - they moved on) is still a huge negative. You are right though, this is somewhat a biased perception and scapegoating is real.
- jongjong 4y agoGreat observation. I think this is often the case with overrated developers. The fact that they churn out a lot of lines of code can make them seem highly productive.
- voiper1 4y agoThis was painful to read.
- darthrupert 4y agoSort of a toxic article, possibly written by a person who thinks they know how people work. However, the writer ignores complexities of humans, and ends up being a rather poor judge of character. (See what I did there) Anyway, snark aside, most people who are changing jobs do so after a long period of deliberation, and when they have made a choice, they will stop taking new responsibilities. Because taking new responsibilities when you know you're leaving would be unprofessional. If someone is good at what they do, they will seem like dead weight on the day they leave. But if you look a year to the past, there should be a different view of accomplishments. Of course, this is not the only explanation for this situation, but a common one.
- patrick451 4y agoThe piece starts off with >I remember having a discussion with a more tenured coworker, with the subject being the impending departure of another coworker. I said, “man, it’s going to be rough when he leaves, considering how much he’s done for us over the last several years.” After list of what these supposedly overrated people do, the piece ends with > If you’re thinking of doing these things, don’t. If you’re currently doing them, stop. I’m not saying this because you’ll be insufferable (though you will be) and I want to defend humanity from this sort of thing. I’m offering this as advice. Seriously. These things are a whole lot more transparent than the people who do them think they are, and acting like this is a guaranteed way to have a moment in life where you wonder why you’ve bounced around so much, having so much trouble with the people you work with. Which isn't a very convincing plea, given that the author himself initially held the exact opposite opinion of a coworker engaging in these behaviors.
- remoquete 4y agoHow is overcommunicating a bad thing in a remote work environment? That post was written in 2013, when most IT companies required to work on site. If you're several time zones away, you do need to overcommunicate. How is promoting your own achievements a bad thing in the context of overcoming obstacles? Why should teams endorse a culture where achievements are not celebrated nor announced? This comments nails it in that taking good stuff to the extreme can be bad. And that's about it. https://news.ycombinator.com/item?id=33759950 https://news.ycombinator.com/item?id=33759950
- maccard 4y agoYou're reading a lot into the headline and not the explanation. For overcommunicating, the real nugget IMO is: > A lot of people mistake activity for productivity I've worked with a few of these people, and they generally tend to be very active on slack/email, make their way into meetings and ensure they're involved in "the process", while derailing every single one of those conversations into tangents, and then slide off into the next cycle of meetings and talking. > How is promoting your own achievements a bad thing in the context of overcoming obstacles? I think you're taking the article to the extreme here a little bit. Again, these problematic people tend to be the ones who talk about how involved they were on system X at $PREV_JOB, and if we need to do something like it again we should talk to them about it. It's not about saying "hey I crushed it this year, here's N things i did really well", it's people who deflect their current lack of progress and work by pointing at their previous achievements. I wish I didn't know this from past experience, but I do....
- remoquete 4y agoI hear you; I also had similar experiences. At the same time, I've had bad experiences with people who never, ever, communicate, to the point that one starts wondering if they're alive. That doesn't help teamwork either. I believe the whole post is more of a projective test than anything else: people read it how they want to read it, because it's vague and full of generalizations.
- thewileyone 4y agoHaving managed several teams in big corporate environments, I have to agree that the squeaky wheels are the ones to watch out for. I learnt this because early on, during performance reviews, I had a sixth sense that I was shafting the quiet ones so I put together a performance metric system based on impact of work. What I found was that the quiet ones were more productive and caused the least negative impact compared to the self-aggrandizing ones. I shared this system with everyone on the team with their own data and slowly the squeaky ones started to transfer out while the team continued to improve productivity and quality because the quiet ones were happier.
- brokenmachine 4y agoBless you, good sir.