Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Cognitive bias cheat sheet

betterhumans.coach.me

Post reply on HN
Print view View original

131–140 of 143 posts

Re: Cognitive bias cheat sheet

#131

Post by dfabulich »

deegles wrote: post #66
adamweld wrote: post #64

Earlier quoted context omitted.

If you are interested in learning how your brain makes decisions, where biases and error come from, and a whole lot more, I highly recommend this book by Nobel Prize winner Daniel Kahneman: https://www.amazon.com/Thinking-Fast-Slow-Daniel-Kahneman/dp... Interestingly, he won his nobel prize in the field of economics, but he's a psychologist, not an economist. His research was so influential that it changed business s…

Do you have any examples around how meetings have changed? I'll need to relay that information promptly...

http://juanreyero.com/article/technology/meetings.html

"The principle of independent judgments (and decorrelated errors) has immediate applications for the conduct of meetings, an activity in which executives in organizations spend a great deal of their working days. A simple rule can help: before an issue is discussed, all members of the committee should be asked to write a very brief summary of their position. This procedure makes good use of the value of the diversity of knowledge and opinion in the group. The standard practice of open discussion gives too much weight to the opinions of those who speak early and assertively, causing others to line up behind them."

(Following this advice is rare; I think it's bold to say that Kahneman's research has already changed meetings.)

Re: Cognitive bias cheat sheet

#133

Post by reitanqild »

CWuestefeld wrote: post #115
taeric wrote: post #72

Earlier quoted context omitted.

I actually get the impression that most of the articles that are "liked" by HN are somewhat grass roots. Take this one. It is a "hacker" that is spending time to try to improve biases held. It is somewhat ironic, to me, that I am basically accusing us of having an anti-intellectual bend. However, it is not unique to psychology. There is a similar slant against "academic" computer science.

There is a similar slant against "academic" computer science. As someone who went to college for CompSci, I see good reason for a slant against computer science . The problem is that it's the wrong topic for somebody who does software development! What we do is not science , it's engineering. Much of the time spent teaching us the science aspect is wasted, at least compared to the opportunity to use the time on engin…

> What we do is not science, it's engineering.

You could argue that for many of us it is Software Carpentry.

I am a B.Sc. in something something computers. I have worked on some serious stuff (real distributed sensor systems across huge geographical areas and another time working on fringes of a soft-realtime image-recognition system).

Much of the time however I feel I'm much more of a software carpenter.

I actually quite enjoyed some of the stuff from "Software carpentry" online course even though I already was an engineer.

Re: Cognitive bias cheat sheet

#134

Post by groovy2shoes »

CWuestefeld wrote: post #115
taeric wrote: post #72

Earlier quoted context omitted.

I actually get the impression that most of the articles that are "liked" by HN are somewhat grass roots. Take this one. It is a "hacker" that is spending time to try to improve biases held. It is somewhat ironic, to me, that I am basically accusing us of having an anti-intellectual bend. However, it is not unique to psychology. There is a similar slant against "academic" computer science.

There is a similar slant against "academic" computer science. As someone who went to college for CompSci, I see good reason for a slant against computer science . The problem is that it's the wrong topic for somebody who does software development! What we do is not science , it's engineering. Much of the time spent teaching us the science aspect is wasted, at least compared to the opportunity to use the time on engin…

> The problem is that it's the wrong topic for somebody who does software development!

For somebody building the next CRUD app, perhaps. In my line of work (EDA software), I routinely apply concepts from my computation science education on the job and in my code. Algorithms, data structures, discrete mathematics, graph theory, set theory, type theory, universal algebra, tractability theory, automata theory — these are all topics where knowledge has come in handy in my professional experience at various jobs.

Of course, concepts from other fields — biology, linguistics, and physics, for example — have also come in handy on occasion. I almost feel like there's no such thing as a "wrong topic for somebody who does software development", though some topics are certainly more relevant/useful than others.

Re: Cognitive bias cheat sheet

#135

Post by known »

Insulate yourself from Machiavellianism (willingness to manipulate and deceive others), Narcissism (egotism and self-obsession), Psychopathy (the lack of remorse and empathy), Sadism (pleasure in the suffering of others)

Re: Cognitive bias cheat sheet

#136

Post by oblio »

groovy2shoes wrote: post #134
CWuestefeld wrote: post #115

Earlier quoted context omitted.

There is a similar slant against "academic" computer science. As someone who went to college for CompSci, I see good reason for a slant against computer science . The problem is that it's the wrong topic for somebody who does software development! What we do is not science , it's engineering. Much of the time spent teaching us the science aspect is wasted, at least compared to the opportunity to use the time on engin…

> The problem is that it's the wrong topic for somebody who does software development! For somebody building the next CRUD app, perhaps. In my line of work (EDA software), I routinely apply concepts from my computation science education on the job and in my code. Algorithms, data structures, discrete mathematics, graph theory, set theory, type theory, universal algebra, tractability theory, automata theory — these ar…

Well, then you're most likely part of minority. And even in that minority I'm willing to bet that a lot of the time is spent in things that have little to do with Computer Science.

Be honest and think of all the time you've spent fiddling with build systems, various random tools (compilers, scripts, databases, version control, etc.).

Re: Cognitive bias cheat sheet

#137

Post by BeetleB »

hairy_man674 wrote: post #127
BeetleB wrote: post #102

Earlier quoted context omitted.

>The psychology replication crisis is much worse than any other field. The article doesn't get into this. Coming from a physics background, I will not say there's a crisis , but: 1. Few research is replicated. 2. We who did physics research were very unconcerned about whether our results could be replicated. Our journal papers were very concise, and it was common practice not to give all the details needed to replica…

>keep the "secret recipe" to ourselves >Everyone will have a list like that You and/or your publishers are terrible human beings.

>You and/or your publishers are terrible human beings.

Eh? Not sure why. Because we have a list of papers we don't believe? It would be naive to believe everything that is published.

I don't like the notion of withholding information, and personally I would not like to accept any paper that does that, but I'm merely stating the norm in the field.

You still have to contend with journal size restrictions. A paper in Physical Review Letters needs to be less than 3 pages. You simply cannot put in enough detail for replication in there. Nature has a page limit of 5.

Re: Cognitive bias cheat sheet

#138

Post by mindfulgeek »

nekopa wrote: post #24

I'm impressed that he managed to figure this out whilst taking care of a baby. When my son was born, I spent most of the wee hours testing which Star Wars theme I hummed worked best for getting him back to sleep. (By the way, The Imperial March worked best, especially slowed down and rocking him on every 4th beat)

I wonder how his partner feels about the experience.

Re: Cognitive bias cheat sheet

#139

Post by stonemetal »

groovy2shoes wrote: post #134
CWuestefeld wrote: post #115

Earlier quoted context omitted.

There is a similar slant against "academic" computer science. As someone who went to college for CompSci, I see good reason for a slant against computer science . The problem is that it's the wrong topic for somebody who does software development! What we do is not science , it's engineering. Much of the time spent teaching us the science aspect is wasted, at least compared to the opportunity to use the time on engin…

> The problem is that it's the wrong topic for somebody who does software development! For somebody building the next CRUD app, perhaps. In my line of work (EDA software), I routinely apply concepts from my computation science education on the job and in my code. Algorithms, data structures, discrete mathematics, graph theory, set theory, type theory, universal algebra, tractability theory, automata theory — these ar…

>I routinely apply concepts from ... theory

Sounds exactly like what I would expect an Engineer to do. Apply theory to the real world. Versus a scientist who I would expect to develop, test, and prove new theories.

Re: Cognitive bias cheat sheet

#140

Post by groovy2shoes »

oblio wrote: post #136
groovy2shoes wrote: post #134

Earlier quoted context omitted.

> The problem is that it's the wrong topic for somebody who does software development! For somebody building the next CRUD app, perhaps. In my line of work (EDA software), I routinely apply concepts from my computation science education on the job and in my code. Algorithms, data structures, discrete mathematics, graph theory, set theory, type theory, universal algebra, tractability theory, automata theory — these ar…

Well, then you're most likely part of minority. And even in that minority I'm willing to bet that a lot of the time is spent in things that have little to do with Computer Science. Be honest and think of all the time you've spent fiddling with build systems, various random tools (compilers, scripts, databases, version control, etc.).

Far too often, to be sure. Two things I have yet to encounter in my (admittedly short, so far) professional career are a sane build system and version control that isn't a PITA...
Post reply on HN