Stories
Slash Boxes
Comments

SoylentNews is people

posted by Fnord666 on Monday April 12 2021, @01:54PM   Printer-friendly
from the it's-harder-to-reverse-engineer-someone-else's-work-than-the-new-stuff-we-just-came-up-with dept.

Here's Why Our Brains Solve Problems by Adding Things, Not Removing:

Have you ever noticed how we usually try and solve problems by adding more, rather than taking away? More meetings, more forms, more buttons, more shelves, more systems, more code, and so on. Now scientists think they might know the reason why.

A study of 1,585 people across 8 different experiments showed that our brains tend to default to addition rather than subtraction when it comes to finding solutions – in many cases, it seems we just don't consider the strategy of taking something away at all.

The researchers found that this preference for adding was noticeable in three scenarios in particular: when people were under higher cognitive load, when there was less time to consider the other options, and when volunteers didn't get a specific reminder that subtracting was an option.

"It happens in engineering design, which is my main interest," says engineer Leidy Klotz, from the University of Virginia. "But it also happens in writing, cooking, and everything else – just think about your own work and you will see it."

"The first thing that comes to our minds is, what can we add to make it better? Our paper shows we do this to our detriment, even when the only right answer is to subtract. Even with financial incentive, we still don't think to take away."

[...] "The more often people rely on additive strategies, the more cognitively accessible they become," says psychologist Gabrielle Adams, from the University of Virginia.

"Over time, the habit of looking for additive ideas may get stronger and stronger, and in the long run, we end up missing out on many opportunities to improve the world by subtraction."

The research has been published in Nature.

Journal Reference:
Gabrielle S. Adams, Benjamin A. Converse, Andrew H. Hales, et al. People systematically overlook subtractive changes, Nature (DOI: 10.1038/s41586-021-03380-y)


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 1) by The Mighty Buzzard on Wednesday April 14 2021, @04:56AM

    by The Mighty Buzzard (18) Subscriber Badge <themightybuzzard@proton.me> on Wednesday April 14 2021, @04:56AM (#1137316) Homepage Journal

    Software: opening other peoples' code and removing stuff is scary - who knows why that interface is provided? What if this code is reused in multiple scenarios that I don't know about? Safer to just add the functionality I need through existing interfaces than to trim an outdated bloated interface because I don't have all the information to know what I'll break by taking stuff away.

    Thus do we have the holy purpose of /usr/bin/grep. Want to know WTF a function, method, or whatever is used by in a project? grep -rIHn --color=always 'functionOrMethodName' $SRCDIR | less -R

    Note: This does not work as well if you're writing a library other people use in their projects rather than an executable.

    --
    My rights don't end where your fear begins.