This weekly roundup thread is intended for all culture war posts. 'Culture war' is vaguely defined, but it basically means controversial issues that fall along set tribal lines. Arguments over culture war issues generate a lot of heat and little light, and few deeply entrenched people ever change their minds. This thread is for voicing opinions and analyzing the state of the discussion while trying to optimize for light over heat.
Optimistically, we think that engaging with people you disagree with is worth your time, and so is being nice! Pessimistically, there are many dynamics that can lead discussions on Culture War topics to become unproductive. There's a human tendency to divide along tribal lines, praising your ingroup and vilifying your outgroup - and if you think you find it easy to criticize your ingroup, then it may be that your outgroup is not who you think it is. Extremists with opposing positions can feed off each other, highlighting each other's worst points to justify their own angry rhetoric, which becomes in turn a new example of bad behavior for the other side to highlight.
We would like to avoid these negative dynamics. Accordingly, we ask that you do not use this thread for waging the Culture War. Examples of waging the Culture War:
-
Shaming.
-
Attempting to 'build consensus' or enforce ideological conformity.
-
Making sweeping generalizations to vilify a group you dislike.
-
Recruiting for a cause.
-
Posting links that could be summarized as 'Boo outgroup!' Basically, if your content is 'Can you believe what Those People did this week?' then you should either refrain from posting, or do some very patient work to contextualize and/or steel-man the relevant viewpoint.
In general, you should argue to understand, not to win. This thread is not territory to be claimed by one group or another; indeed, the aim is to have many different viewpoints represented here. Thus, we also ask that you follow some guidelines:
-
Speak plainly. Avoid sarcasm and mockery. When disagreeing with someone, state your objections explicitly.
-
Be as precise and charitable as you can. Don't paraphrase unflatteringly.
-
Don't imply that someone said something they did not say, even if you think it follows from what they said.
-
Write like everyone is reading and you want them to be included in the discussion.
On an ad hoc basis, the mods will try to compile a list of the best posts/comments from the previous week, posted in Quality Contribution threads and archived at /r/TheThread. You may nominate a comment for this list by clicking on 'report' at the bottom of the post and typing 'Actually a quality contribution' as the report reason.

Jump in the discussion.
No email address required.
Notes -
If the estimator knows that they're consistently high, why aren't they adjusting the model they're using to produce estimates with to account for that?
If the estimator is wrong consistently but in a predictable way... they should be able to be wrong less often?
When I say "account for that in planning", I don't mean you adjust your forecasts downward X% from the report because they always overestimate by the same margin. Consistently high is not the same thing as 'always high' or 'consistently high by the same amount'. It just means that on average the estimator is greater than the true value (or, really, the quick estimate tends to be higher than the slow estimate).
Not necessarily. Estimation is always dealing with real world constraints liked limited resources and time frame for gathering and analyzing data, sampling bias, unknown unknowns, etc...
I encourage you to read the Nate Silver article I linked. He talks about this significantly more articulately than I can.
I am somewhat familiar with Nate Silver's approach to modelling and prediction.
And I'll reiterate the general critique.
If you damn well know your model is going to be inaccurate, include error bars, express how much irreducible uncertainty there is. At least acknowledge that the number is most likely incorrect and is subject to large revisions, downplay confidence.
Actually, it looks like they DO have that option on display and HOLY CRAP the bars are really large on some of these.
Maybe its not a particularly useful estimate if businesses are looking for something something reliable to act upon.
More options
Context Copy link
More options
Context Copy link
Do you want to be the guy in the office who adds in the unprincipled empirical fudge factor to a statutorily mandated report? The verbs in 29 USC 2 are “collect, collate, report, and publish”, nowhere does it say “estimate”, “calculate”, or “determine”.
I'd be the guy in the office suggesting "hey we can publish the report, and show both the standard estimate and the estimate with the empirical fudge factor side-by-side so its clear we're not hiding the ball."
More options
Context Copy link
More options
Context Copy link
At least in this case I think there is an added political dimension of reluctance to update the model: "You were happy enough to overestimate [measurement] for my opponent last term, and now you want to publish lower estimates, maybe even underestimates on my watch. Are you trying to display partisan bias?"
In addition to the value of "we've at least measured it consistently for the last century, even if there are known issues with it it's easier to fix those in post", which also has some value.
More options
Context Copy link
More options
Context Copy link