Good point. It is my experience with both of my teenage kids, diagnosed with adhd.

In general, it needs to be broad since it is difficult to predict if you get enough attention or not.

So starting with a very short explanation helps increasing the odds of that it will be processed.

Explainations need to be 2-3 short sentences. Longer, and even teenagers with Ahdh may not follow or retain the explanation offered.

I find that most LUA code sits between functional, imperative and OOP.

What works well is to measure the same food multiple times in a container (every time same volume ).

after a while you can estimate carbs by visually inspecting the contents without scale.

Add to that automatic bolus by a semi closed loop system to correct for errors, you can achieve good results with minimal effort.

For closed loop better cgms will help.

Main points are (fsl2 based):

- latency, currently 10min.

- accuracy, fine in normal range, but when you have a low blood sugar suddenly the latency spikes a lot.

- values when being under the shower too high.

- start up time of 60min could be lower.

-open up the hardware for any app to read