If you haven't read "Thinking, Fast and Slow" it really summarizes the problems in a lot of decision making in a very clear way.
I'm still reading through, but, you have two major actors in your brain. A "fast" side, and a "slow" side. The fast side makes gut decisions, and the slow side, well, applies more complex judgements and can include a more unbiased view of the world. There's a ton to this process, but importantly, the fast side is very happy to jump to conclusions when presented with missing information.
The lesson of Moneyball, then, was that the "fast side" thinking clouded judgements of baseball prospects by filling out ridiculous statements like "he's got a hot girlfriend, must be able to have the confidence we need on the field".
I'm not sure how you can use the baseball metaphor in terms of software design, though.
But, you could easily say that we're presented with an incomplete amount of information when building software. (What's going to happen when it runs? Who knows! Just build a nice API and continue.) So we definitely all probably have a lot of "quick learning" techniques and processes we just adopt to. For example, Googling before you just stop and think. Or using the UI techniques of other applications, because "that's how the big profit-making companies do it".
I'm still reading through, but, you have two major actors in your brain. A "fast" side, and a "slow" side. The fast side makes gut decisions, and the slow side, well, applies more complex judgements and can include a more unbiased view of the world. There's a ton to this process, but importantly, the fast side is very happy to jump to conclusions when presented with missing information.
The lesson of Moneyball, then, was that the "fast side" thinking clouded judgements of baseball prospects by filling out ridiculous statements like "he's got a hot girlfriend, must be able to have the confidence we need on the field".
I'm not sure how you can use the baseball metaphor in terms of software design, though.
But, you could easily say that we're presented with an incomplete amount of information when building software. (What's going to happen when it runs? Who knows! Just build a nice API and continue.) So we definitely all probably have a lot of "quick learning" techniques and processes we just adopt to. For example, Googling before you just stop and think. Or using the UI techniques of other applications, because "that's how the big profit-making companies do it".