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 -
Perhaps you should read the link, discussing variability in the calories out portion. Saying that CICO is thermodynamics and that there is variability at least in CO is perfectly consistent. I'm not sure what windmill you think you've slain.
I will not call you a liar, but this is indicative of the mindset with which you are entering this conversation. You have tarred the people you hate with a scarlet letter and then simply closed your mind to any meaningful discussion. Very bad epistemic hygiene.
I don't hate CICO advocates, I just don't know if there's a constructive conversation to be had with people who consistently respond to everything with "you're lying" or "you must have missed something". This is also epistemic closure - anyone who struggles with CICO is always accused of lying.
As I've already said I did get some benefit from calorie tracking. I think it's useful even just to learn how many calories are in your food. So of course, I don't hate CICO, but of course this kind of defensiveness is also very typical of CICO advocates.
If the defense of CICO epicycles is that "uh, actually sometimes people just burn extra calories for no reason", that's not that compelling. Isn't the point of CICO that it should always give you predictable results, and that if your results are wrong, it's because you made a mistake or are lying?
You're mashing up two different things which should be clearly distinct at this point in the conversation. There is no epicycle that there is variability in CO. There is just variability in CO, given the things we are generally able to control for. That's just the data and the labels we have to go with it. I've seen some attempts to quantify things like calories consumed by individual organs and how that correlates to their sizes and such, but on a population scale, we're basically never going to have measurements like that to control for, nor is an individual likely to go to the effort of taking precise measurements that could, in theory, more precisely predict individualized CO. So, absent that, we take a few factors that are easily measurable, fit the curves, see that they work pretty well, with some variability. Before, you had been claiming that this population-level variability was flatly denied by your enemies. Now, you think it's an epicycle. These are both Obvious Nonsense claims. This is just data and empirics.
Now, what you're stuck on is the second part, given that the population-level curves aren't able to precisely control for everything, how do these curves and the variability they contain provide predictable results for individuals? Well, you need individualized observational data to figure out where you are within that variability. The population-level curves get you close, but if you want precision, you need good individualized observational data. My experience with tracking for my wife and I is that the data is extremely noisy and must be handled with care. But after that care, the trend line is, indeed, 500cal/day = 1lb/wk, only with very noisy measurements. I don't think either of our maintenance levels from the trend line were precisely what the population-level data predicted, but they were both pretty close, and our tracking decisions were probably suitable to explain the minor deviation. It's this part, after you've already gotten a lot of individual observational data to avoid the population-level variability problem, where the vast majority of people (and all tightly-controlled lab experiments) get predictable results. The population-level variability doesn't magically jump into this part as an epicycle.
My actual experience of CICO was exactly the opposite. It worked initially but when I tried to bulk, I found it predicted weight gain very poorly. Since CICO is of course, perfect and never wrong, it must have been a mistake I was making, and since I couldn't find my mistake, I decided to spare myself the stress and anxiety and stopped tracking.
I am sorry you had that experience. Unfortunately, it is probably unlikely that I will be able to figure out whatever was going on in your individual case through comments. But I'm not sure what is supposed to change about my understanding of the published literature from your example.
FYI, my personal experience included periods of gaining, and my trend line from the noisy data was bang on at 500cal/day = 1lb/wk on that side, too (and my wife's). But I'm not sure how you might/might not want to update your understanding of the published literature based on my example, either.
I have a similar understanding of the published literature to you, I think - but knowing that planes crash when their altitude decreases is not enough to avoid crashing a plane. The published literature tells us, for example, that calories out should probably exceed calories in by about 500 and then you'll lose weight. But as I've heard in this thread there is no reliable way to measure either, calories out has been shown to change in response to calories in, so you are in effect chasing a constantly moving target.
What useful information are we left with? Pretty much, eat more or less until you get the desired change in weight, and that "more or less" refers specifically to calorie content. Which is a reasonable start.
But all this amounts to is a fine motte. The actual bailey of CICO is that everyone who follows a calorie tracker and gets an incorrect result is lying or denying science, that it's physically impossible to fail to lose weight on 1800 calories or to fail to gain weight on 4000 calories, and that hormones don't affect weight.
Good news! The CICO folks that you dislike have entire articles on how this works, what the ranges are, how to understand it, etc. To steal a little bit of the plane analogy from below (not adopting it entirely), when a plane uses fuel, its dynamics change, too. That doesn't mean that physics don't work or that we can't understand how to use the system effectively.
Much more than that. Once you dial in where you are within the population-level variance, you get remarkably good predictions for how the noisy process works. I have a lot of background in stochastic systems, too, and I think this part trips a lot of people up. It's not easy to filter noisy data appropriately or to even understand the right timescales to pick for your filters. That's why the CICO people don't jump to an imaginary bailey and instead do things like creating an app that has a lot of filtering built-in.
Even though my degrees are actually in aerospace, I'm not sure the plane analogy is the best one for this part. Instead, maybe let's push things to a bit of an extreme with an analogy to semiconductor fabrication. In this case, someone could have some familiarity with the published literature in semiconductor physics, could go through a variety of published patents, but then when they try to make their own semiconductors, they fail. One response could be to claim that everyone in semiconductor physics is lying to them or just blaming them for doing it wrong; that those baddies are claiming that semiconductor physics "just works and must be perfect" or whatever. Another response could be that there are parts of the process that do require some specialized background knowledge to do precisely, perhaps some experience with tuning certain processes along the way that aren't always shouted to the rooftops in the public domain.
I think that careful filtering of CICO data also requires some mathematical experience if you want mathematical precision. I haven't actually used the particular app that I linked, nor am I privy to the tuning/filtering decisions they've made, but I'm familiar with the work of the guys who made it, so I have a reasonable amount of trust that they're doing a pretty good job at tuning it in a way that will work pretty well for most users. But the good news is that most people don't need mathematical precision here (unlike in semiconductor fabrication). I think @07mk goes a bit overboard in how wide of an error bar is needed, but for most people, you really can just hand-tune a bit with a little fudge factor, not needing to be super precise on your filtering, and see the results. But at the same time, if you do get into the details of tuning filters well (or offload that work to something like that app that probably does that ok enough for you), then you probably do get pretty precise predictions.
A lot of this comes down to error analysis and ranges for estimation. One group of CICO-haters say that it's just flatly impossible to filter in a way that gets you even remotely close to usable data without metabolic ward precision. Another group of CICO-haters say that any quantity of error violates their strawman that "CICO is perfect in every way". Most of the time, they don't put numbers to their error ranges. They don't put any numerical analysis tools to the question of how much data must be collected to achieve some O(epsilon) error or how different filtering schemes affect this. Frankly, many do fall into a small number of common 'traps', just like how undergrads in a numerical analysis course often fall into a small number of common 'traps'. I am lucky in that I have the toolset to get a lot more mathematical precision than most people, so I don't have to learn all of that from scratch or trust somebody else's filter. And when I did those things for an n=2 experiment, knowing all of the caveats about how noisy things are and how difficult the numerics is, my technical assessment was that I was shocked by how precise it turned out to be.
Well, what can I say - good for you. Personally, I find that calorie counting does not work very well for predicting weight gain, even after a year of trying it. And if it's true that label calories can be as little as half of the actual content, and it's not possible for a normal person to measure calories out, then perhaps I shouldn't be surprised. As they say, garbage in, garbage out. If you put in garbage data, and you get an impossible result like a TDEE of 4000, then is it actually reasonable to persist?
It seems like false precision to me. CICO advocates call for weighing every leaf of lettuce and drop of oil. When estimates of calorie content can be off by so much, how is that not false precision? Particularly in the context of weight gain, it's not even rational to refuse to eat food that can't be measured.
That's not true.
I mean, it is possible. Lots of people do manage it well enough. Just like lots of people manage to pass their numerical analysis class, even if there is some number of common 'traps'. It's only a few people who get bitter enough after falling into a common trap to decide that the professor is full of bullshit and the material is impossible, then dropping out of the class. Even apps do it pretty darn well these days.
We get it; you're a very accomplished strawmanner. You don't need to keep making bigger and bigger strawmen to try to prove some point. We didn't count almost any vegetables (some exceptions).
More options
Context Copy link
More options
Context Copy link
More options
Context Copy link
More options
Context Copy link
More options
Context Copy link
More options
Context Copy link
More options
Context Copy link
More options
Context Copy link
More options
Context Copy link