The post is about Mark Hyman not Huberman.

It is a video of an interview between Huberman and Hyman.

Even if you don't like Huberman, it's very worthwhile to learn from someone like Hyman.

I agree that Mark Hyman is very worthwhile.

I just disagree that "not about Huberman" is accurate as a description of a long conversation between Huberman and someone else.

This guy advocates for 0 sugar intake, which seems like a very fringe opinion…

I prefer fringe than stupid.

Perhaps that was true 50 years ago, but in an increasingly complex technological world, problems simply cannot be solved without increasingly advanced engineering skills.

The overwhelming majority of software engineers are building garden-variety CRUD apps.

Engineering might be a commodity if you're "building garden-variety CRUD apps"

But a lot of companies aren't - or at least, they don't think they are.

Which is like saying most software is reading, modifying and writing memory. Technically true, but not at the level it tells the story.

If that was really true, the world would need only ONE generic CRUD app. It just needs to operate at scale.

You can create a timer with one transistor and an LC feedback loop.

Almost all civil, chemical, electrical, etc., engineering emerged from a practice-first, theory-later evolution.

How many thousands of lines does your AI-generated frontend code have?

Do you have to maintain the code?

Everyone knows that to understand metabolism you should use a parser.

I've already tried Paul.

Check my previous submission.

I upvoted.

In general HN doesn't like you editing titles other than simplifications to get them under the 80 char limit.

In your case without looking at the details I can believe there is a line connecting keto to what they're talking about "Brain Reductive Stress and Impaired Energy Metabolism" but I don't see it in detail.

I see interesting stuff for this PubMed search

https://pubmed.ncbi.nlm.nih.gov/?term=psychosis+ketogenic+di...

where the title matches your thesis. Writing a blog post that references a few articles and explains the connection and linking that would also be a good idea.

You probably can use these physics to measure many other molecules in a continuous non invasive way.

This will be a revolution in personalized medicine.

Ketones next please.

A search tells me its for type 1 diabetics. Are there other applications, like keto dieters?

Huge market for endurance athletes. Just like heart rate and blood oxygen, blood glucose is a definitive marker whether you're going to fast or not. Having that information allows you to perform at the very edge your body is capable of performing, without ever exceeding that limit and crashing out.

There have been blood glucose sensors using needles for a long time, and many sports banned them because they are a huge advantage - but they didn't want to de-factor force every athlete to constantly prick an IV under their skin and then run around with it for hours.

Once those come in smart watches, every semi-advanced runner (and those who'd like to feel like one) will need one.

Endurance athletes are a small market and the market for endurance athletes who would benefit from a CGM is even smaller.

> every semi-advanced runner (and those who'd like to feel like one) will need one

This, however, is the truth. Every semi-advanced runner (and wannabe) knows that they need to run more, run slower on most of their runs, run fast occasionally, and eat well in order to improve their performance. But they’ll buy literally anything that might offer them an “edge” instead.

> Endurance athletes are a small market and the market for endurance athletes who would benefit from a CGM is even smaller.

It's not that small. Garmin made billions in revenue here, expanding it on the process. Most of their customers don't really need blood oxygen either, but they all have it anyway.

Many chronic illnesses are currently being researched as a KD treatment target.

Continuous ketones measurement is a big deal.

Wouldn’t a digital servo mitigate the problem?

No, they were digital servos. As far as I know the only difference between analog and digital servos is in how they process the received signal, the signals themselves are very much the same.

But if by digital you meant some hypothetical servo that needs to receive its data as bytes with a checksum — yeah that would work, as long as the thing can do a graceful shutdown on powerloss. But I am not aware of such servos (although I wouldn't be surprised if they existed, on that project I was just a programmer).

I realize now my comment was dumb.

Thanks for the correction.