Has anyone looked at computer programming, and mapped it to cognitive biases? Any mapping at all would do - whether it's a mapping of common errors to biases, or of common methodologies
Tell me more
×
Programmers Stack Exchange is a question and answer site for
professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.
|
|
|
Given the inaccuracy of most software schedules, there's possibly an extremely common planning bias. It might also be true that a good portion of a programmer's preference for a particular programming language and software methodology is due to the exposure effect or bias. |
|||
|
|
|
Looking through the link you provide, pretty much all of the example biases are applicable. As an example: Planning fallacy - I've seen a lot of developers under estimate project times. End result is code that's rushed, with a resulting drop in quality. Normalcy bias - This could almost be YAGNI described as a problem rather than a solution. Clustering illusion - Developers spotting patterns that don't exist, then creating a clever storage optimisation absed on their dellusional understanding of the pattern. Result is code which doesn't support the first case that breaks the expected pattern. |
|||
|
|
|
I'd say many of anti-patterns can be linked to cognitive biases. |
|||
|
|
