Live data from Hacker News

How I keep myself alive using Golang

bytesizego.com

111–120 of 136 posts

Re: How I keep myself alive using Golang

#111

You've set up a torture loop for yourself instead of listening to your body and the existing medical device. And you are now piping medical biometric data through both Google Calendar and your Apple watch.

Ya know, people deal with life-changing events in their own ways.

Re: How I keep myself alive using Golang

#112

Sorry 1/2 into the article all that kept popping into my head is someone tell this man about a cgm like a dexcom . It all of this out of the box . My wife has been a t1d for 30 years the dexcom cgm makes all of this a lot better

I wrote the article- I’m very aware of Dexcom and it doesn’t have all this out the box

You probably know all this as well, but for future googlers:

I used to use Libre + MiaoMiao + Nightscout, but these days I much prefer Dexcom G6 + xDrip + Nightscout.

Pros for the G6:

- No 3rd party transmitter (e.g. the MiaoMiao)

- It's smaller and can go on the stomach so it's less likely to get ripped off

- 1 less app involved -- xDrip integrates directly to Nightscout and there is no need for the Dexcom app

- Supposedly the glucose readings are a bit more accurate than the Libre

Cons:

- Sensors are more expensive than the Libre

- The transmitter is not rechargeable so you need to keep buying them every 90 days

Re: How I keep myself alive using Golang

#113
T1D here, I had to abandon the Dexcom as it had an unsilencible alert for "your sensor will expire in 6 hours", that on top of only 10 day sensor life pushed me over to the Libre 2. I now realize I could've just started the sensor in the early evening to have those alerts during the day, but I've survived 40 years without alerts. To avoid alerts I use the Libre2 reader and then use Juggluco app on my android, that was the one good thing about the Dexcom was that it could pair more than one app or device, where the Libre can't pair more than once per sensor life. Random personal tips for better reducing the impact of low blood sugar. Eat unsaturated fat as a condiment, especially olive oil. I feel this gives me a non glucose energy source. I'm going to have to dig deep and find an alternative as the world's olive harvests are plummeting and prices are starting to spiral up. The other thing I do is take a few puffs of THC around dinner time. I don't want it affecting my daytime and it's neuroprotective effects last 24 hours and don't require much. Finally learn to use supplements and insure a good diet and supplement nutrient intake to have the rest of your systems running as well as possible. I have been taking Melatonin nearly every night since June of 1995. Melatonin upregulates insulin receptors and allows for me to take about 40% less than typical. It is a problem with the Lantis I take as I need to take only 11.5 units and have to use a needle and even then nudge my dose to a very specific spot that varies sometimes with different needles.

Re: How I keep myself alive using Golang

#114
post #86
post #13

I just wanted to add that your writing style is wonderful and that this was a pleasure to read. Incidentally, I work in pentesting, and one of my colleagues has Type 1 Diabetes; your overview of it and its resultant complexities really made me empathize with what challenges he has to surmount daily while still being one of the nicest, most approachable people in our team.

Yes... you can lead a normal life with diabetes (you can even be a top level tennis player - https://en.wikipedia.org/wiki/Alexander_Zverev#Personal_life ), but this article really made me appreciate the level of self-discipline it takes to do that.

Several NFL players play/have played with Type 1.

Re: How I keep myself alive using Golang

#115
post #20

Incidentally, I created something related to this yesterday. A tmux plugin to display your glucose data as a status icon in your terminal. As a T1 myself, I use a Dexcom as my CGM and have it working around that specifically, but I'd love to open it up to other devices too, and offer more. Feel free to check it out! https://github.com/Cian911/tmux-xdrip

I wish Dexcom could sync directly with a watch. I've been waiting on that for years but I guess it would drain the watch battery.

Re: How I keep myself alive using Golang

#116
post #49

Great article! While I haven't done anything as involved I have found using technology to track health issues to be empowering myself. I'm curious about your thoughts on insulin pumps. I'm not very familiar but I know a few people with T1 that use them and seem happy with them. My understanding is that the idea is that they both monitor glucose levels and supply insulin to keep things stable. Have you considered them…

Pumps still require a fair amount of planning, experience, and knowledge about one's T1D in order to use effectively. The pump can only be reactive: sugar spikes, emit insulin. Sugar tanks, sound an alarm. You're supposed to tell it in advance how much sugar you're about to consume in order to keep things level, and they can't anticipate you deciding to exercise.

Re: How I keep myself alive using Golang

#117
I put the picture of the hamburger and fries in GPT-4 chat and asked for the total carbs in it. With some caveats about double-checking, it gave:

>Typically, a standard cheeseburger with a bun, beef patty, cheese, lettuce, and tomato can contain around 30 to 40 grams of carbohydrates, primarily from the bun. A standard serving of fries could add an additional 30 to 50 grams, depending on the serving size. Hence, the meal in the image could contain somewhere between 60 to 90 grams of carbohydrates in total.

That is pretty good! Good luck with your T1D, my got his diagnosis 5 years ago and it's pretty amazing technology we have for it now.

Re: How I keep myself alive using Golang

#118
post #82

Earlier quoted context omitted.

Difficult to hide your diabetes when you wear a sensor on your arm and have to inject insulin throughout the day

Actually, the sensor is super easy to hide (especially with long sleeves) and injecting is also quite discreet these days. I've seen injectors that are about the size of a marker or a wireless earbuds case. It's easy enough to go to the bathroom right before lunch or when you get an notification on your phone.

I'm not diabetic but I'm pretty sure what you describe would cause a lot of stress, especially if you don't want anybody in the office to find out... "hey you have a small bladder maybe?" Stress has an impact on sugar levels, making it harder to regulate. If you think knowing of the medical condition is bad for your career at your current employer, maybe it is better to switch employers.

Re: How I keep myself alive using Golang

#119
Very Cool!

I also have T1D and its a natural source for cool software engineering projects like this.

You might like these two posts: Using machine learning to predict when I excercised: https://dddiaz.com/post/glucose-datascience/

Using Genomic Software to explore my auto-immune genes: https://dddiaz.com/post/hla/

Re: How I keep myself alive using Golang

#120
post #3

I talked to Matt about not owning our own data after GopherConSG where he gave this talk. It was enlightening how complicated the issue is - there's a lot of legal liabilities on the end of the data provider (the company that monitors the glucose) so I can understand why larger corps are a bit hesitant to open up. On the other hand, it seems quite heinous that users don't have access to data that is rightfully theirs…

I never understood this. Would this be like buying a BIC pen and they have a required license agreement where any entropy made with the pen is owned not by the creator of the data but by the creator of the tool used? With out the person the data would not exists.

I don’t think it is like that at all.

Perhaps if your bic pen fed your scratches into a system that ignored aberrant marks, cleaned up your letters, ran a spell check, and printed the result in the font of your choice?

This glucose device is a sensor. Sensors generally produce noise, sometimes a lot of noise, and require post processing in order to get the signal you wanted. The raw data is interesting but often not reliable as input.

That kind of processing is usually complex and companies often seek IP protection and close their source or use DRM. Whether that’s good or bad is a matter of opinion but the motivation is clear.

Post reply on HN