Hacker Newsnew | past | comments | ask | show | jobs | submit | more guzik's commentslogin

> It's not sexy, and as a result an overwhelming majority of the population is unaware about how to avoid succumbing to it

When I started building an ECG Holter in my early 20s, I tried to get some friends to use it and kept hearing "yeah, but it’s not exactly sexy to wear that thing." That’s when it hit me how little people care about prevention until something goes wrong. We still have a huge awareness gap to close.


I asked a heart doctor for a calcium scan. He said I didn't need that, but he wanted me to wear a Holter monitor for a few days (reasons unknown). I did not.

That was years ago. I have different doctors now but still no calcium scan. Time to ask again possibly.


So I went on X after a long break from social media, and my feed is full of tips like this one:

Growing on X is so simple I’m shocked it works.

100x comments a day

10x posts a day

15x DM’s a day

1x thread a day

1x email a day

This is how you grow your presence on X.

Even if having a presence matters, how can you actually say something meaningful if you post 10 times a day - there's no way (unless you just repeat yourself). Hopefully my algorithm's just gone weird but sadly the people I used to follow stopped posting.


Hey, can you join our Discord: https://discord.gg/sPay3Xm? Reach out to me personally (@guzik1) - happy to help you with that as we've already had a few people who integrated with rpi, so I can share some tips and examples.


Thank you! We've integrated a different chip for measuring chest movements


sadly, comfort for chest straps compared to hand straps is a known issue and ours is definitely no different. Wve done a bunch of tests, tried different materials/custom solutions, and honestly we're still clueless how to make it significantly better (if anyone here works in textiles or wearable fabrics, I'd love to connect). So yeah, if wearing your Garmin for more than an hour already feels uncomfortable, ours probably won't be much better in that regard


for regular users, since the device itself doesn't have any interface, we need to send at least some data so they can see it somewhere. the natural place is the phone, but not all of our professional clients liked viewing long ECG recordings or detailed metrics on a small screen, so we built cloud access mostly for convenience .

(to be clear - if a developer wants, they don't need to send anything to us)


Thanks! Yep, the interface for a shell is available here: aidlab.com/developer/debug we are using Jquery Terminal + Web Bluetooth (sadly, I think it's not under active development anymore)

and yeah, when we started years ago, it felt natural that the next step would be to measure glucose from blood but the truth is with the current state of science, it's still not possible to do that 100% non-invasively.


we don't have any plans right now to build a blood glucose sensor (although we already support a few external sensors - but not glucose monitors yet)


how about the blood preasure?


I am glad that we decided to pick CSV as our default format for health data (even for heavy stuff like raw ECG). Yeah, files were bigger, but clients loved that they could just download them, open in Excel, make a quick chart. Meanwhile other software was insisting on EDF (lighter, sure) but not everything could handle it.


And at this point, "lighter" is immaterial.

"Hi, I'm sending you a two-line statement in a Word document. It's 10kB."

"Thanks, I took a screenshot of it and forwarded it. It's now 10MB."

"Great! That's handy!"


We thought for a long time about using protobufs in our product [1] and in the end we went with JSON-RPC 2.0 over BLE, base64 for bigger chunks. Yeah, you still need to pass sample format and decode manually. The overhead is fine tho, debugging is way easier (also pulling in all of protobuf just wasn't fun).

[1] aidlab.com/aidlab-2


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: