Live data from Hacker News

How Bullshitters Not Just Survive But Thrive (2016)

linkedin.com

21–30 of 99 posts

Re: How Bullshitters Not Just Survive But Thrive (2016)

#21
post #19
post #13

Earlier quoted context omitted.

The pomodoro technique is quite popular. Also, goals, systems, etc. There are a few subreddits that focus on things like this.

I've tried the pomodoro technique. It's very good for deadlines. Academia doesn't tend to have genuine deadlines at the junior researcher level so it's basically just a matter of finishing the work whenever you can. What would be nice, is if there was a way to somehow gain intrinsic motivation to do stuff that interests you? I get extremely excited about projects at first and then tail off. I'm not a "finisher", and…

I had this problem when i was a PhD student. Towards the end of my time, i started doing something which fixed it, and which i could have been doing all along: make a list of the figures for my paper, and do whatever bit of work moves the next most important one towards being finished.

I should mention that i was working in cell biology; in cell biology, you earn career points by publishing papers telling a new story, where papers comprise a series of figures, each one showing results which demonstrate some point of your story. Papers also have an introduction, description of the results, and discussion, but those are pretty much filler. The smart scientists i know read the title, the figures, and the materials and methods section. Perhaps not every field is like this.

So, to make a good paper, you have to come up with a series of good figures, which means (a) finding a story you want to tell, (b) working out what points you want to make, and (c) getting results which make those points. Having done that, there's the technical work of making up the figures (learn to love Illustrator), and some writing, and you're done.

Finding the story is usually the easy bit. Your supervisor usually has some untold ideas for stories floating about, or there will be some variation on an existing story that people will enjoy hearing. Or you might just need to spend a year or two trying stuff, which can be fun until it suddenly isn't.

Working out what points you need to make takes time, but once you know the story, is usually not too hard. Crucially, you don't need to know up front that these points are all true. As you work towards them, if you find any that aren't true, you just throw them away, and either replace them, do without them, or change the story a bit.

It's getting the results which is hard. That is the actual work in scientific research. Designing, performing, interpreting, and refining experiments. Finding, preparing, and characterising materials. Learning or inventing techniques. Spotting weaknesses and plugging them with control experiments. Endless, seemingly incessant, tea breaks.

Having a concrete list of the figures you need helps you keep going at getting results, and helps you do the right ones. Before i had a list of figures, i did all sorts of experiments because they seemed interesting, and connected to what i was doing, but which could never have contributed to my paper.

Re: How Bullshitters Not Just Survive But Thrive (2016)

#22

> Can you see a cow? Looks like a blurred Japanese painting. I see 2 samurai, one standing on the left, one dead on the right (face down, you can see his hair). I can't explain the horn helmet the standing samurai is wearing, though. > If you still can't see the cow, please search "visual intelligence cow" in Google images Oh. A cow indeed. (It's head, facing the camera.)

For anyone who, like me, still couldn't see the bloody cow:

https://boldquestions.files.wordpress.com/2014/01/cow-outlin...

Re: How Bullshitters Not Just Survive But Thrive (2016)

#23
post #5

Ironically, this article also reeks of bullshit. The massive characterization: the sloppy nerd (W-S), the consummate bullshitter (S-W), and the "rare" real talent (W+S). Which sets up the classic, "you're successful, so you must be a bullshitter" (because those S+Ws are sooo rare ). The "CB's" he's describing are so incredibly transparent, they might as well be strawmen.

> The "CB's" he's describing are so incredibly transparent, they might as well be strawmen. Strawmen or not, I've worked for two. Those aren't fond memories.

Yup. It takes a while to see the abstract pattern underlying their behaviour. Once you see it, its very clear. But for a long time you're distracted by the details of day-to-day events and you think they're just another co-worker with some annoying habits.

I'm confused why so many commenters are quick to shout "B.S" on this article (are they BSers in hiding?) but maybe he is oversimplifying too much. True S-W types are pretty rare and are probably evidence of some extreme psychological disorder. (E.g., malignant narcissism or sociopathy. Robert Hare is a researcher in criminal psychology and wrote a book on such people: https://www.amazon.com/Snakes-Suits-When-Psychopaths-Work/dp...).

Re: How Bullshitters Not Just Survive But Thrive (2016)

#24
The lens the author is looking through is missing the other side of the coin.

Communication:

Regardless of how smart you are, if you can't communicate it to others, then then value of your intelligence is limited to an individual role. People who can't/won't communicate make terrible managers. The people above them have no idea what's going on in their team. Poor coordination with other teams creates issues outside of their team. Their own team members will fail to understand what role they are playing in a larger effort. The non-communicating manger will know (because he's in the meetings), but will fail to pass that information to their team. As you move up the chain of command, communication becomes more important than what you as an individual can produce.

Confidence:

Your car breaks down. It's critical you have it working tomorrow. Two mechanics show up.

- The first mechanic says: "This is really tricky. I don't know if we can get this fixed tomorrow. It may take a week. I'm not sure"

- The second mechanic says: "This is no problem. I'll have it fixed by tomorrow".

Which one are you going to hire?

Perception:

The hardest pill to swallow is that upper management is very aware of what's going on in a team, especially when the manager is a problem.

  - upper management has usually seen it all before.  So any behavioral issues are easily spotted.  
  - Team members complain to people on other teams, and word gets around.
  - Team members will request re-assignement or discuss quitting.
There are a lot of ways to handle a bad manager, some good, many bad. The more professional you are, the easier they are to handle (i.e. be honest, don't participate in rumors, don't complain about others, own your responsibilities, be transparent, and communicate with facts)

Performance over Perception:

Performance is always more important than perception. The issue is a lot of employees don't understand what the priorities are for their organization.

The priority is almost always. How efficiently and predictably does the job get done. Efficiency also includes how much hand holding someone higher up has to do.

Re: How Bullshitters Not Just Survive But Thrive (2016)

#26
post #5

Ironically, this article also reeks of bullshit. The massive characterization: the sloppy nerd (W-S), the consummate bullshitter (S-W), and the "rare" real talent (W+S). Which sets up the classic, "you're successful, so you must be a bullshitter" (because those S+Ws are sooo rare ). The "CB's" he's describing are so incredibly transparent, they might as well be strawmen.

I think that many good, effective managers would end up in the "bullshitter" basket by the definitions of this article: they delegate work (they better!), they do not work themselves if you define work as writing code or spending time in the lab, etc.

IMO effective managers should be doing exactly that -- surround themselves with smart people, delegate and make working conditions fulfilling and enjoyable for their teams.

Re: How Bullshitters Not Just Survive But Thrive (2016)

#27
I mean, I feel like everyone hating on this article either:

1. has never had the misfortune of working with one of these people. "poser" devs who care more about "communicating up" and making a show of their (often quite trivial) contributions

2. has worked with people like this, but doesn't perceive the behavior described in the article, for whatever reason.

A couple times in my life, not just in software, I have worked with people who are _exactly_ like the article describes. The work they do is all perception-management stuff. Shuffling around work tickets, setting up/attending meetings, etc., when they are supposed to be individual contributors. Meanwhile, they contribute nothing. I've even had a coworker -- a peer -- come to me to ask me to do a task when they were assigned to do it. Because they were busy organizing work tickets.

Don't get me wrong. You have to toot your own horn when you do something that should be noticed. Your boss won't always recognize when you've made a meaningful contribution, so saying, "Hey I did this and it's pretty good, and it adds value to our org in these ways" is not inherently bad.

It's when that autotooting is to bring attention to stuff outside what they're _supposed_ to be contributing that it should raise red flags. Or when they start trying to delegate work to their peers. I'm really glad so many of you find this article so awful because it means you've never felt the frustration of watching someone like this get praised for and advance by essentially doing nothing.

edit: I don't know how to explain it to someone who hasn't ever noticed it. The behavior pattern in the article is not something a lot of people notice. But among people who do notice -- at least those I've talked to -- it's very obvious and really bothersome.

That said, most of the time coworkers -- even really smart, kind, hard-working coworkers -- either don't notice or don't care. So it's not surprising to me that commentators here think the article is BS. You've probably sat next to people like this but you didn't notice. Good on you.

Re: How Bullshitters Not Just Survive But Thrive (2016)

#30

I mean, I feel like everyone hating on this article either: 1. has never had the misfortune of working with one of these people. "poser" devs who care more about "communicating up" and making a show of their (often quite trivial) contributions 2. has worked with people like this, but doesn't perceive the behavior described in the article, for whatever reason. A couple times in my life, not just in software, I have wo…

I work with a person like this now. He actually doesn't delegate a great deal despite being a project lead. He snows people with jargon, is often late to meetings, rarely comes into the office, and has produced no usable contributions in years. If I had acted as he does at any of my previous jobs, I would have been fired.

I truly don't understand why he still has his position. The sad thing is that he'll probably get promoted.

Post reply on HN