Talk idea: behavioral science/psychology in software

[codetojoy]

A Slack thread mentioned this article by jbrains. Quote/paraphrase:

Don't ask: "what did you do?". Ask: "what did you achieve?"
I love linguistic tricks that encourage better behavior.

I'm no expert (and perhaps this is well-covered in the Summerside Book Club?) but behavioral economics (or "behavioral science", or broadly, cognitive psychology) is about behaviour, and the idea above motivated me to jot this down. IMHO, there is potential insight/familiar techniques for programmers.

e.g. 1 We don't choose between X and Y. We choose between descriptions of X and Y. Even trained doctors will prefer a procedure if it is described as being "90% successful" over "10% unsuccessful". (see jbrains quote above)
e.g. 2 When working together, person A can usually detect when person B is making a systemic error (hello, pair-programming!).

I'm not sure I've got this talk "in me" right now, but thought I would document it, in case someone else wants to take it.

Good books include: Misbehaving and Thinking, Fast and Slow . (Both authors have won the Nobel Prize, yet the books are mainstream.)