loading...
Cover image for Have you read Thinking Fast and Slow?

Have you read Thinking Fast and Slow?

thejamespinto profile image James Pinto Updated on ・1 min read

Q: Have you read this book? Or would you like to? Did you finish it?

Q: What good lessons do you think developers can get from this book?

Like and share this if you want me to write a full-length article on this book tailored for developers.

medium: https://medium.com/@thejamespinto/have-you-read-thinking-fast-and-slow-6a68a7054daa

Discussion

pic
Editor guide
Collapse
ben profile image
Ben Halpern

I read it a few years ago and I forget what specific lessons I learned, but I definitely came away with a new type of deliberate thought process.

I’ve read that some of the science in the book doesn’t totally hold up, but it’s definitely fascinating food for thought.

Collapse
thejamespinto profile image
James Pinto Author

I'm writing a "30 minutes short" article on tailoring techniques from this book to everyday dev environments. You'd be glad to know the first 15 minutes is entirely about the deliberate thought process part.

I'm collecting ideas now. What parts of everyday dev routines would you like to read about in deliberate slow motion? :)

Collapse
itsjzt profile image
Saurabh Sharma

Just a few pages but the "soap Vs soup" was really interesting.

Collapse
thejamespinto profile image
James Pinto Author

I'm writing a "30 minutes short" article on tailoring techniques from this book to everyday dev environments. The soup/soap part was mentioned in the topic of priming effects.

I'm collecting ideas now. What parts of everyday dev life would you see best helped if software companies were better able to prime their developers before working?

Collapse
matt_chabert profile image
Matthieu Chabert

I guess for most people :

Have you read it / Do you want to read it? Yes

Did you finish? NO

Collapse
thejamespinto profile image
James Pinto Author

I'm writing a "30 minutes short" article on tailoring techniques from this book to everyday dev environments.

I'm collecting ideas now. What parts of everyday dev routines would you like to read about through slow-thinking lenses? :)