I've been working in this space for seven years, this isn't new. There have been big studies from the UK in 2020 [1] and Israel in 2015 [2] about this.
Some of my learnings:
- Don't start your day with a large amount carbs. Have some insulin in your blood before eating that big bowl of oatmeal. Or just go for some yougurt with nuts and seeds.
- The classical order of a three course meal (salad first, then main dish, then dessert) is pretty good in terms of preventing glucose spikes.
- Going for a walk after a meal is great for bringing glucose levels down.
- Eat at least 2h before going to sleep. Having high glucose levels disrupts sleep.
- Alcohol lowers the glucose response of a meal, but is still bad unfortunately.
- Diet Coke works. No spike vs loads of sugar with a real coke.
- Stress can spike glucose like crazy, e.g. being in an interview or during takeoff.
- If you really want to know how you react to some food, keep the circumstances (time of day, sleep, physical activity, stress) similar. There's too much influence beyond just the meal.
I bet that everyone who is wearing a premium smartwatch or an Oura ring now will be using a CGM now and then in the next years.
Yeah they bought veri.co last year and announced the integration of metabolic into their platform last week.
As the authors mention in the end, personalized nutrition based on CGM only makes less sense than also integrating sleep, stress, movement,... - which Oura is really good at.
> I think we will still need software devs, but not as many as we do today.
I'm more of an optimist in that regard. Yes, if you're looking at a very specific feature set/product that needs to be maintained/develop, you'll need less devs for that.
But we're going to see the Jevons Paradox with AI generated code, just as we've seen that in the field of web development where few people are writing raw HTML anymore.
It's going to be fun when nontechnical people who'd maybe know a bit of excel start vibe coding a large amount of software, some of which will succeed and require maintenance. This maintenance might not involve a lot of direct coding either, but a good understanding of how software actually works.
I'm not surprised. Apple ID seems completely broken to me, even when I just tried to set up a new MacBook 4 weeks ago:
Create an account via the settings page? Had to contact support because my phone number + email got stuck in some "halfway activated but can't log in" state.
Sign into the App Store + downloading some software? Got stuck in some broken form that wouldn't let me enter payment information. Had to crawl through reddit threads about how to work around this mess, just to be able to use the App Store.
Can't help but wholeheartedly agree. You would think that the bit where you actually gave them money would be buttery smooth, but each one of those interfaces is riddled with bugs and yank. Every time I have the misfortune of needing to touch them, I know I'm in for a world of pain.
I'd be fine calling myself a "AI Engineer" for having worked with TensorFlow, PyTorch and scikit-learn and having experience in running AI Models in production.
Nowadays, making requests to the API of a LLM provider is what makes an engineer a good fit for working at an AI company? Really?
Cold emailing someone who makes their contact information publicly available and might be interested in a sales pitch is not illegal in Europe. Sending SPAM is. The lines get even more blurry with automated AI tools that offer personalized sales pitches as a service.
I'd be curious how this plays out in court. Probably something like:
- If you use an AI tool to scrape leads and to generate the content but then still send out individual emails from your Mail provider, it's still a cold email.
- If you use an AI tool and also automate the email delivery, it should be considered spam.
> Does this mean that I should private my GitHub-mirror to my personal blog, because this can become a common thing? I have removed my email from my GitHub-profile now, but they can probably get it from my Git-log anyway...
It's possible to use a noreply.github.com linked to your username for making commits. And you can to change the authorship of past commits in your own repos with write access.
I try to avoid give my email in a public and processable format whenever possible.
This article reads as if the author was exploring the "Gervais Principle" [1] with Sam Altman as example.
> Of all organization men, the true executive is the one who remains most suspicious of The Organization. If there is one thing that characterizes him, it is a fierce desire to control his own destiny and, deep down, he resents yielding that control to The Organization, no matter how velvety its grip… he wants to dominate, not be dominated…
Early this year, I've received a hostile PR for a "maintenance only" JavaScript authentication library with less than 100 stars but which is actively used by my employer.
It added a "kinda useful but not really needed" feature and removed an unrelated line of code, thereby introducing a minor security vulnerability.
My suspicion is that these low quality PRs are similar to the intentional typos in spam emails: Identify projects/ maintainers who are sloppy/ gullible enough and start getting a foot in the door.
Apples Stock price is has pretty much remained flat YTD whereas Google, Meta and Microsoft have ballooned thanks to the AI hype.
> The executive team is saying "the best thing we can think of to spend this money on is shrinking the company". That's not a good sign, even if they are also spending big on R&D.
As an executive, buying back shares makes a lot of sense if you believe that your company is currently undervalued and you have a large cash pile.
Tim Cook seems to be very optimistic about Apple's future [1], so doing a buyback in the current market might be a smart move.
Some of my learnings:
- Don't start your day with a large amount carbs. Have some insulin in your blood before eating that big bowl of oatmeal. Or just go for some yougurt with nuts and seeds.
- The classical order of a three course meal (salad first, then main dish, then dessert) is pretty good in terms of preventing glucose spikes.
- Going for a walk after a meal is great for bringing glucose levels down.
- Eat at least 2h before going to sleep. Having high glucose levels disrupts sleep.
- Alcohol lowers the glucose response of a meal, but is still bad unfortunately.
- Diet Coke works. No spike vs loads of sugar with a real coke.
- Stress can spike glucose like crazy, e.g. being in an interview or during takeoff.
- If you really want to know how you react to some food, keep the circumstances (time of day, sleep, physical activity, stress) similar. There's too much influence beyond just the meal.
I bet that everyone who is wearing a premium smartwatch or an Oura ring now will be using a CGM now and then in the next years.
[1]: https://pubmed.ncbi.nlm.nih.gov/32528151/ [2]: https://pubmed.ncbi.nlm.nih.gov/26590418/