Same here, I have first.last since 2005: every combination of dots or not are aliases to my first.last and cannot be registered.
There a thousands of first last in the world, and apparently, all of those that have a gmail account are also quite bad at giving their email address... ^^ They probably have firstlast123 and the numbers evade!
I receive things daily, from simple accounts miscreated (thanks for the one month Netflix account 6 years ago) to plane tickets, notarized acts for land sell, medical things etc. I tried to respond etc. but no one understands that I'm not their recipient. Crazy.
Having high glucose levels won't kill you in the sort term, yes. But we cannot compare pre-diagnosis high blood sugar level (the body had that for months so it is accustomed to it) to the suddenty of it with cutting off insulin. In fact, things can spiral out quite quickly.
You see false low glucose figures, that last, you start reducing your slow acting insulin, you skip some fast acting insulin. Within 24h, ketoacidosis starts and you can start feeling nauseous. At some point, if you eat, you vomit. You are cornered: you don't have the carb intake to inject insulin, and you can't eat. Even worse, at some point, if you drink, you vomit, so you dehydrate, and it's a matter of hours to live. Shit happens fast, things can get critical is a few days.
Diabetes management is complicated, this is far from exact science, and having a good knowledge of everything is hard. I was already bitten by this cycle of nauseous feeling with slow acting skipped a few month after my diagnosis. I learnt to never ever skip slow acting insulin, even when blood sugar is through the floor. Prepare some apple juice and still go on.
I have Freestyle Libre 2, and it is quite a disappointing thing software-wise. I have to reverse engineer another app to get an API for my data, I have to go through Internet to get my blood sugar level (for a standalone display for example, so I can't make one that works "off grid", like... in my plane), they do sparse updates, they lag behind OS version by dizains of month for their apps, they have 10s of apps/websites, it is hard to understand. So I'm not surprised by poor bug management.
I wish some big names invest in a CGM device. Don't make it medical (even medical grade ones like Abbott & co say you have to check with a finger thingy device, so why bother), make it $500 one time plus $10-20/month, make it open about the data and you'll get everyone. Maybe no one want to invest because in 10/20 years Diabetes will be a thing of the past?
Well it is not quite a mutable vs immutable strings war, nor Ruby being late to the party or something like that.
The move is so we can avoid allocating a string each we declare and use it since it will be frozen by default. It is a big optimization for GC mainly. Before we had to do such optimization by hand if we intend not to modify it:
# before
def my_method
do_stuff_with("My String") # 1 allocation at each call
end
# before, optim
MY_STRING = "My String".freeze # this does 2 allocations with 1 at init being GC quite early
def my_method
do_stuff_with(MY_STRING)
end
# after
def my_method
do_stuff_with("My String") # 1 allocation first time
end
But this move also complicates strings manipulation in the sense of it will lean users toward immutable ops that tend to allocate a lot of strings.
foo.upcase.reverse
# VS
bar = foo.dup
bar.upcase!
bar.reverse!
So now we have to be deliberate about it:
my_string = +"My String" # it is not frozen
We have frozen string literals for quite a while now, enabled file by file with the "frozen_string_literal: true" comment and I've seen it as the recommended way by the community and the de-facto standard in most codebase I've seen. It is generally enforced by code quality tools like Rubocop.
So the mutable vs immutable is well known, and as it is part of the language, well, people should know the ins and outs.
I'm just a bit surprised that they devised this long path toward real frozen string literals, because it is already ongoing for years with the "frozen_string_literal: true" comment. Maybe to add proper warnings etc. in a way that does not "touch" code ? I prefer the explicit file by file comment. And for deps, well, the version bump of Ruby adding frozen string literals by default is quite a filter already.
It is sorta late to the party. Common Lisp has similar with regards to how lists are done. Specifically, it is not uncommon to make a static list like `'(1 2 3)`. Doing this, however, has implications on what operations you can do on the data elsewhere.
I say sorta late to the party, as I think it is more than fair to say there was not much of a party that folks were interested in in the lisp world. :D
I do. It's a whole thing that get you down to writing your business logic in an expressive way very easily. Framework (Rails) helps, yes, but even pure Ruby can be nice. I've written a second time accuracy simulator for cars and chargers in a EV charging stations in pure Ruby, that was fast to iterate around and pleasant to write.
The ecosystem, toolchain and all do a lot. It is really missed when I do other languages, and I wish to find the same way of developing elsewhere. I currently do C for embedded in an horrible IDE, and I want to bang my head against the table each time I had to click on something on the interface.
- We are also designing and developing a more advanced family of microcontrollers, RP235x, which we expect to launch in the second half of 2024, as well as chipsets for use in our SBCs and compute modules for release thereafter.
- We continue to invest in the design and development of new SBC products, including successors to Raspberry Pi 5 and Raspberry Pi Pico, that will incorporate future semiconductor products, including RP235x. We intend to develop new products that address customer requirements such as industrial temperature tolerance and onboard non-volatile storage. We also intend to continue working to extend the long-term availability of our older SBCs
This means on-board flash !
- We are designing and developing a family of microcontrollers, RP235x, which will serve as successors to RP2040, and which we expect to launch in second half of 2024. RP235x products are designed to operate at higher speeds, use less power and provide greater security than RP2040.
Yeah I sure hope they will fix that ADC. I hope they will fix it on the RP2040 too. That would be great to use the RP2040 as peripherals for a more powerful chip (and load the code/pio through the swd ports so you don't need flash for each of them).
This will likely not happen, this chip is made to be integrated and there are many advantages to QFN; including the ability to make much smaller boards. See: https://includemicro.com/tiny-rp2040/
The foundation has made a lot of work to reduce board sizes as they are major contributors to water waste in a project (they also are the majority of the weight).
That would be nice to also optimize SELECT DISTINCT foo FROM bar. It is usually very poor on big tables and we have to do recursive CTE. This comes a lot with admin builders for filters (<select >).
SELECT DISTINCT has seen quite a bit of work over the past few years. As of PG15, SELECT DISTINCT can use parallel query. I imagine that might help for big tables.
I assume the recursive CTEs comment is skip scanning using an index and looking for the first value higher than the previously seen value?
Certainly skip scans would be nice. There has been some work in this area, but not recently. As far as I recall some other infrastructure needed to go in first to make it easier for the query planner to understand when skip scanning would be useful.
But with neuropathy, which causes loss of feeling, pain… in the feet for example, you can ignore damage that combined with a loss of blood circulation capabilities can make things deteriorate very badly (necrosis, amputation).
For me, the main thing keeping at being good at the closed loop system is delay. In the pancreas, « measure » and delivery happen at the blood level. It is instant. With CGM and pen or pomp insulin delivery, it is in the superficial higher layers of the skin for which you have 15min delay to and from blood.
Well, Netlify went south by forcing businesses (including ours) to migrate from Pro to Entreprise plan (which is very pricy) by having a hard limit on the members of the Pro plan. We were forced to migrate, then we migrated away to pure AWS a few month later.
We don't know what happened there. Did they have money issues?
One thing AWS has done well is charge enough out the gate that they don’t need those “good news” posts where companies jack rates up. Google maps, but many business focused apps I’ve used too end up squeezing ridiculous price increases through. I’ve not experienced that with AWS.
reply