Live data from Hacker News

The forecasting fallacy (2020)

alexmurrell.co.uk

31–40 of 71 posts

Re: The forecasting fallacy (2020)

#31

There's a germ of insight here that could use some development and nuancing. > The future is uncertain. You cannot predict it. But you can create it. For millions of years, prediction has been the engine by which humans have created the future. We don't always call it that, but prediction is the engine. Let's start from the most basic facts of life. We know from experience (our own and others') what plants will susta…

Also to your point, it makes no sense to say, "You cannot predict it. But you can create it." The reason a person or entity creates something is that they've predicted a desired outcome for that creation.

> It seems that we need to figure out what separates the kind of prediction that is the engine of human life and progress from the kind that is just useless blather.

For sure. The author treats content marketing by management consultancies — blather — as serious efforts to predict outcomes. But these are stories about potential outcomes created to lure customers to the rim of their sales funnel. In other words, their actual prediction is that publishing thousands of "thought leadership" pieces will improve SEO and sales engagement, which is probably true.

Re: The forecasting fallacy (2020)

#32
post #22

Earlier quoted context omitted.

There's a wide variety of strategies available. The type you mention of picking up small inefficiencies certainly exists but there are plenty of other strategies that involve having some sort of informational edge. Some hedge fund managers just read a lot of earnings releases, but there are also more sophisticated approaches: a famous example would be the fund that paid for satellite imagery of the parking lots of ce…

Both of those examples have been exploited to death and no longer are profitable

If a feature is used by many and has a predictable impact on their behavior it becomes profitable again.

If you act faster on the same feature as everyone else, or you predict the feature accurately, you can anticipate what the market will do in response.

The market often overreacts to new data. So if satellite imagery shows steep decline in parked cars, the stock will be predictably oversold. You can then take a contrarian position (buy the stock before it reverses to the mean).

Some commonly used features by popular public trading bots create predictable market movements, no matter if the feature itself is long-term informative/profitable.

Re: The forecasting fallacy (2020)

#33
post #14

The author would also conclude: * Collision avoidance systems are terrible at forecasting collisions because they almost never result in a collision. (The point of the system is to help you avoid an upcoming collision.) * The prediction that Y2K would happen was a bad one since it didn't happen. (We spent billions of dollars to make sure it didn't.) * The 1978 prediction that the ozone layer would be depleted by 2010…

It's like saying if you drive tomorrow you're going to get in a fatal accident, no one in their right mind would drive in that case.

The only way it can work is if you make the prediction and don't tell those that are affected. But generally in any larger market attempting to capitalize on the future state of the market changes the market and the predicted position.

Re: The forecasting fallacy (2020)

#35
post #27
post #14

The author would also conclude: * Collision avoidance systems are terrible at forecasting collisions because they almost never result in a collision. (The point of the system is to help you avoid an upcoming collision.) * The prediction that Y2K would happen was a bad one since it didn't happen. (We spent billions of dollars to make sure it didn't.) * The 1978 prediction that the ozone layer would be depleted by 2010…

> The author would also conclude: > The prediction that Y2K would happen was a bad one since it didn't happen. (We spent billions of dollars to make sure it didn't.) I would argue that we don't really know what would have happened had the world not spent all the money on upgrading systems. It appears a very large number of them would have continued to work as expected and it isn't immediately clear if the ones that w…

The people who were working on Y2K did know what would happen in many cases. Their work avoided known huge messes in banking, infrastructure, aviation, and healthcare, among others.

What they didn’t do, much, is write or blog about their work. A lot of fixes were to commercial or government systems running on commercial or government hardware. Publicly disclosing problems and fixes was not part of those cultures.

So it is very hard, today, for members of the public to go back and reconstruct the problems and solutions to “prove” that there were real issues. Which has led some people to believe, incorrectly, that there were not real issues.

Re: The forecasting fallacy (2020)

#37
Much of the discussion here including the linked article fail to make an important distinction between domains. Prediction can be done quite effectively on thin tailed processes. A lot of the counter examples listed in the comments here are physical systems which are thin tailed. I see aircraft autopilot, collision detection, ozone depletion. These are all well understood physical phenomenon in which large deviations do not occur — your car doesn’t get teleported elsewhere in the middle of avoiding a collision. If a large deviation did occur, say a meteor striking between your car and the object it is attempting to avoid, the collision avoidance system would almost certainly fail. These events occur so infrequently that the system can just assume they won’t and boast a high success rate.

Meanwhile the examples from the linked article are fat tailed processes. Recessions, GDP, interest rates, exchange rates. These are all subject to large discontinuous jumps. Anyone doing a 5 year rate prediction in July 2019 would have been required to predict the pandemic in order to accurately forecast. This is a single example but predictions in this domain are regularly blown out by being teleported to a completely different world. Unlike the thin tailed domain these events happen frequently enough that they’re the only thing that matters for the forecast.

Knowing which class your generating process belongs to is critical to understanding whether forecasting will be effective or not. I’ll take collision detection and leave economic forecasts at the door any day.

Re: The forecasting fallacy (2020)

#38
Some questions from an economic analysis standpoint.

If someone can predict the future reliably, why don't financial firms hire them? If a firm did hire them, how much money are they getting paid? why so little? Is the economic value of correct predictions lower than you'd think? Does the market believe "past performance is no guarantee of future results"?

Re: The forecasting fallacy (2020)

#39
Ugh. This annoys me.

Can we predict things super accurately? Often no. But you know what’s better than anecdotes about times predictions were bad? Training and testing sets to judge how good we expect models and predictions to be from the beginning. Because a lot of these are not high confidence predictions.

And no, it’s not “black swans”. Are those a thing? Sure. It’s ok that models can’t account for things that are not modeled or seen before. But if these things are common enough that they’re systemic and the mode is just not actually accommodating for the world of relevant factors, then it’s not going to have been a good model on the test set to begin with. And we would know that.

Re: The forecasting fallacy (2020)

#40

Much of the discussion here including the linked article fail to make an important distinction between domains. Prediction can be done quite effectively on thin tailed processes. A lot of the counter examples listed in the comments here are physical systems which are thin tailed. I see aircraft autopilot, collision detection, ozone depletion. These are all well understood physical phenomenon in which large deviations…

It's not that we can't forecast heavy tailed processes -- it's just that the forecasts are used wrong.

The appropriate layman's forecast of a recession within the next year is something like a constant 11 %. I'm willing to bet this outperforms most "predictions" out there.

But! When people see that number they go, "right, so it's vastly more likely it does not happen" and then completely ignore the possibility. The problem is not in the probability, but in the failure to adequately assign a cost function to the less likely outcomes.

Post reply on HN