tlubinski

The CCC had a nice talk last year about the data VW collects and what can be learned from it (all the data was unencrypted accessible): https://media.ccc.de/v/38c3-wir-wissen-wo-dein-auto-steht-vo...

(unfortunately it's in German - but there is an english live translation available)

130 comments and no one mentions "The Sting"? https://www.youtube.com/watch?v=_nAIb_J9T5M

Because the engineers of the University of Waterloo haven't shown any clinical data yet.

It's not approved yet anyway. But if you are ever in Berlin, let me know and I'll give you a tour.

We - at DiaMonTech - are working on non-invasive glucose monitoring for over a decade now. It's a hard and complex problem and as long as clinical data is missing, I'm very sceptical.

We just reached (in a clinical trial) a comparable accuracy as early-stage invasive devices that got FDA approved with a shoe-box-sized device and we still have some work to do. The pre-print of our publication is here: https://www.researchsquare.com/article/rs-5289491/v1

I'm excited to see new developments but in this case, I'm not sure this will reach the market anytime soon.

They just launched a new high-speed train from Berlin to Paris with a travel time of 8 hours: https://apnews.com/article/germany-france-berlin-paris-highs...

Last Chance to See by Douglas Adams - it's a book from the early 90s and Douglas Adams travels the world to see the world’s most endangered and exotic creatures. It's heart breaking and at the same time written with such a delight that it is fun to read. I cannot explain it better but highly recommended.

Just started "Babel: Or the Necessity of Violence" after the whole controversy about the book (see: https://news.ycombinator.com/item?id=39099914) - enjoyable read so far, but can still go both ways.

The IMHO gold standard book to get an understanding of the history of non-invasive glucose monitoring and the different technological approaches is "The Pursuit of Noninvasive Glucose: Hunting the Deceitful Turkey" by John Smith: https://www.researchgate.net/profile/John-Smith-241/publicat...

We - at DiaMonTech - working on a solution with mid-infrared spectroscopy and showed good accuracy in a published paper in the "Journal of Diabetes Science and Technology". We plan another clinical trial this year, but yes, this took some time. We started in 2015 and still have some work to do.

The Billion Dollar Code tells the story about an artist and a hacker who build Google Maps before Google Maps. It plays in Berlin, Germany in the 90ies and I really liked the vibe of the whole mini-series. Also the combination of Art and Technology and getting the most out of current technology makes it a good "hacker" series.

I enjoyed "Rise of the Centaur", a documentary about a company that develops an intel compatible microprocessor.

we are working on it (www.diamontech.de) but our device has still the size of a shoebox. I don't think there is a device in a smaller form factor out there that can measure glucose non-invasively (at least with a decent accuracy).

CargoLifter tried that (https://en.wikipedia.org/wiki/CargoLifter). Founded in 1996, went public around 2000 followed by insolvency in 2002. Their production hanger is now a tropical holiday resort (https://www.tropical-islands.de/en/).

He was born as Kim Schmitz

Hey, we developed a new way to detect blood glucose non-invasively and wrote down how it works.

With DiaMonTech (www.diamontech.com) we are also working on a non-invasive blood sugar monitor. Google lens was always a discussion with the interested parties (e.g. investors). Our take was that it is hard to detect the small concentration of glucose in tear fluids but even if you manage to do that, the real problem would be that there is always a delay (between 30 and 100 minutes) until changes in the blood sugar level are seen in tear fluid. So for people with fast changing blood sugar levels (i.e. diabetics) the needed information comes too late.

Yes, I'm still reading this and I'm not afraid of working by the rules (or learning them). I'm just surprised how fragmented the whole embedded device stack is. The whole software development process could (and should) be more defined. Let me gather some more experience and see if I can come up with something more clever :).