StevenTM

StevenTM t1_j2e198b wrote

IF works just fine for people over 40, what on Earth are you on about?

Edit: and no, a "slowing metabolism" is not a thing that exists before your 60s, on average, and it's not the reason people gain more weight in middle age (late 30s - early 50s), or have more trouble losing it. Barring medical conditions, your metabolism slows at a predictable rate, but is mostly stable between age 20-60.

https://www.health.harvard.edu/blog/surprising-findings-about-metabolism-and-age-202110082613

> these results strongly suggest we may no longer be able to blame weight gain in middle age on a slowed metabolism.

4

StevenTM t1_iw4gxco wrote

Why isn't it possible to just create a copy of the weights for task 1/task 2 at various points, or even continuously?

Storage space is ridiculously cheap, and even high powered debugging traces (like Microsoft's iDNA (TTT Debugging), which basically captures full process dumps in millisecond increments (albeit for a single running process) aren't THAT huge.

Then when you re-run task 1, it just uses the weights from the latest snapshot for task 1. I don't see why it wouldn't or what the benefit of using the (obviously mismatched) weights from task 2 would be (while running task 1).

I mean.. i know it sounds like a stupidly obvious suggestion, and I'm fairly certain it isn't used as a solution, but can't figure out why

3