I don’t. I use the right macros… But I thought I was pretty clear in the end.
MAN. About everyone uses the raw weight as we have no other options and it MATTERS if it loses a ton of water or not.
Give me an example, seriously. Actually, you gave me one, the chicken. You wrote:
Why is it a problem if I use THIS, raw data for my 200g chicken breast? Tell me. It makes no sense that you don’t understand these trivial things.
I have my 200g chicken breast and use the data mentioned (or whatever is in my own database, probably something very close so either is fine and not exactly like reality but close enough).
So I ate 57g protein and 2.4g fat. You wrote these data so WHY would it be wrong?
I couldn’t care less how much my meat will weigh after I cook it. Why would I weigh it, that’s unnecessary work. I use the raw weight, 200g. Just like about everyone… It’s how one does it. (If we don’t eat it all, that’s a bit more weighing but we use the raw data as a starting point and derive everything else from it.)
What problem do you see in that? Using the correct info, why is it bad in your eyes?
I already wrote that if you think I use the cooked weight with the raw macros, you are obviously wrong. It’s not how one track, every proper CICO site explains it to you.
I could even eat my meat raw (okay, I wouldn’t do that with chicken or pork… some people do).
Many people eat meat raw.
They ONLY have raw data and they still can track right enough
It doesn’t even matter if I cook it or not, the macros will be the SAME. For the thing, not per 100g, why would I care for cooked macros for 100g when I eat it all at once (or half of it, still don’t need that info)?
I still I am pretty sure that everyone of us tracking use raw macros as WHAT ELSE? It’s the only one accurate available… Except if we calculated cooked macros from raw ones (it still started with raw) or when we buy cooked food with a label, obviously.