top | item 35041871

(no title)

madelyn-goodman | 3 years ago

I really like this point, that fast thinking is shallow. I think there should be more respect for having to think deeply about things and process before coming to conclusions. I think that is more of a sign of intelligence than just responding to something right away.

discuss

order

Jensson|3 years ago

Answering quickly or thinking deeply first doesn't have much to do with intelligence, some smart people answer quickly and other thinks first. It mostly have to do with how much you care about being right, if you are deeply afraid of being wrong you will think a lot first before answering since you prefer spending all that energy over being wrong, while if you don't care you just answer now and think later.

Speaking before you think makes you look dumb, but it doesn't make you dumb. You see the difference? You might have met many such people who were smart, but that you identified as dumb since they weren't afraid of appearing dumb.

lamontcg|3 years ago

Lots of people used to think that Obama pausing for thought meant that he was taking time to cook up lies in his head.

Skilled liars are usually quick though because they're not considering if something is correct or not, they just need to figure out what kind of thing to say to make you agree with them.

motbus3|3 years ago

I tend to agree that thinking models are per se shallow. But I don't even believe much in thought models to be honest. I believe they are just heuristic for decisions and do not constitute the whole thinking process itself. But maybe I am wrong

posix86|3 years ago

I don't think you can generalize like that, at all.

A better sign of intelligence is knowing when thinking deeply is in place. And most often it's not. Most often it's more cumbersome to think for a long time than making the occasional mistake.

People that think long & hard about everything don't have their priorities right.

JohnBooty|3 years ago

Again, it really depends.

If you're doing a research or fun project, where failure has no consequence? Then yeah, mess around, move stuff, go fast, break things. Worse is better.

There are so many situations where there are, consequences, though. Either because failure is pretty dang bad, or (perhaps more commonly for our industry) a mistake will increase our tech debt. Our failure to spend a few extra hours thinking it through in the short term might lead to hundreds of hours of tech debt or (in the extreme case) our entire project/company to fail in the long run.