It’s not the same thing. He is allowed to give them away and is doing so. If Mora is in breach of contract, maybe a better remedy for the distributor would be monetary damages but that is not obvious.
There’s an interesting question of if the distributor misrepresented the deal to Mora as he claims, but from the summary it appears nothing related to that is recorded that the court finds legally relevant.
Why would you use a PPO? The average SWE can be on an HMO. HMO's are fine. I have never once regretted choosing an HMO.
Additionally, you're using the average software engineer salary in the US but then picking California for rent. The article you linked says country wide you'd expect $1950 for renting a 1-bedroom not the $2500 number you are picking for a studio in the bay area.
So you're off by something like $1000 per month (edit: I admit I am simply looking at what I pay for HMO, it's possible that is somehow unrepresentative but I doubt it) by picking the most expensive health plan and mixing up national salaries vs very expensive areas.
The gun violence risk is vastly overblown. The page you are linking to cites a study where gun deaths are being accumulated for ages 1 to 24 years old. Gun deaths are highly non-random and concentrated in older ages and in very specific areas (largely related to gang activity). The average software engineer with family is not going to run into any of that unless they are in the habit of leaving loaded weapons around the house.
This doesn't have that much to do with the genetic heritability of intelligence, which is a measurement in proportion to environmental variability. Civilizations with farming, metallurgy, etc. showed up independently in many places although at highly varying times due to human dispersal. You can also see that intelligence isn't all its cracked up to be from an evolutionary point of view since it sometimes goes down. Has it gone up in most places over the last few thousand or ten thousand years overall. I think so, read the recent Reich paper (EDIT: this Reich https://reich.hms.harvard.edu/publications). But it doesn't only go up all the time.
Disease factors were probably the biggest factor in selection until very recently (and maybe now is just a temporary blip before a return to the historical pattern). Disease almost wiped out the Native Americans and strongly held sub-Saharan Africa back.
Where are you getting 20% from? That's not what Plomin is saying in what you are replying to. Are you confusing the fraction of GWAS estimate heritability out of total heritability (10/50 = 20%) with a top or bottom bound?
Although it's possible for someone with type 1 to have an A1C below 6%, it's very difficult. I've known a few people like that, and they are all super users. It's also going to depend somewhat on the lab running the A1C test, personal biology (A1c is not only affected by blood glucose levels) etc. 6-6.5% is superb control! Parent should be very proud. 6.5-7% is still very good, I haven't looked at the distribution of A1c's for T1D recently, but that would be much better than median which I think is above 8%.
Especially with kids, it's difficult since you don't control how much they decide to eat making pre-bolusing meals challenging (part of why reducing carbs tends to be helpful for people is it reduces the need to pre-bolus and makes it less risky since you need less up front meal insulin).
You can die on the order of hours to days not of high blood sugar per se, but of the low insulin causing diabetic ketoacidosis parent comment mentions.
It would be odd for a faulty sensor to cause an otherwise bad day into dka and death though. The sensor would need to be wildly off for hours and the user to not notice. Insulin delivery would need to be paused or greatly reduced for many hours. There are additional therapies like SGLT-2 that could make this more likely but they usually aren’t used with T1D precisely because they break the normally very strong correlation between inadequate insulin levels (leading to dka) and high blood glucose.
Even though I can’t think of an easy way for a false low(s) to turn into lethal DKA, that doesn’t mean it didn’t happen. Abbott sells a lot of CGMs. It could have been a contributing factor to several deaths even if the fault would almost always not be a significant issue.
My experience has been there is no correlation between skill at teaching and skill at research; maybe the two are even anti-correlated. To some extent, this is an artifact of the selection process for professors, but I think it's partly because there's a real tradeoff between spending effort on research vs teaching.
In some cases, an excellent researcher even has cogent papers but is absolutely abysmal at lecturing and in person teaching skills.
Peers are very important, but from talking to others, it's harder to know where you will get good peers than you would think. Even 1st tier universities will have majors dominated by students whose primary interest is in maximum grades with minimum work and where cheating is rampant. You've got to either get lucky (I did) or put in some leg work to find smart students who are actually interested in learning and doing things right.
I think how much rote memorization is encouraged or required is strongly dependent on the field. Pre-med students will sometimes memorize their way through calculus; a professor I knew once described it as "grimly impressive".
Making invalid states unrepresentable may be a great idea or terrible idea depending on what you are doing. My experience is all in scientific simulation, data analysis, and embedded software in medical devices.
For scientific simulations, I almost always want invalid state to immediately result in a program crash. Invalid state is usually due to a bug. And invalid state is often the type of bug which may invalidate any conclusions you'd want to draw from the simulation.
For data analysis, things are looser. I'll split data up into data which is successfully cleaned to where invalid state is unrepresentable and dirty data which I then inspect manually to see if I am wrong about what is "invalid" or if I'm missing a cleaning step.
I don't write embedded software (although I've written control algorithms to be deployed on it and have been involved in testing that the design and implementation are equivalent), but while you can't exactly make every invalid state unrepresentable you definitely don't punch giant holes in your state machine. A good design has clean state machines, never has an uncovered case, and should pretty much only reach a failure state due to outside physical events or hardware failure. Even then, if possible the software should be able to provide information to intervene to fix certain physical issues. I've seen devices RMA's where the root cause was the FPU failed; when your software detects the sort of error that might be hardware failure, sometimes the best you can do is bail out very carefully. But you want to make these unknown failures be a once per thousands or millions of device years event.
Sean is writing mostly about distributed systems where it sounds like it's not a big deal if certain things are wrong or there's not a single well defined problem being solved. That's very different than the domains I'm used to, so the correct engineering in that situation may more often be to allow invalid state. (EDIT: and it also seems very relevant that there may be multiple live systems updated independently so you can't just force upgrade everything at once. You have to handle more software incompatibilities gracefully.)
That's a hard one because it depends on what sort of details you let into types and maybe even on the specific type T. Not saying what I'm asking for is easy! Units and shape would be preserved in all cases I can think of. But with subranges (x - x) may have a super-type of x... or if the type system is very clever the type of (x - x) maybe be narrowed to a value :p
And then there's a subtlety where units might be preserved, but x may be "absolute" where as (x - x) is relative and you can do operations with relative units you can't with absolute units and vice versa. Like the difference between x being a position on a map and delta_x being movement from a position. You can subtract two positions on a map in a standard mathematical sense but not add them.
I'd be happy for just ranges on floats being quick and easy to specify even if the checking is at runtime (which it seems like it almost will have to be). I can imagine how to attach precision error/metadata when I need it with custom types as long as operator overloading is supported. I think similarly for specialized matrices, normal user defined types and operator overloading gets tolerably far. Although I can understand how different languages may be better or worse at it. Multiple dispatch might be more convenient than single dispatch, operator overloading is way more convenient than not having operator overloading, etc.
A lot of my frustration it is that the ergonomics of these things tend to be not great even when they are available. Or the different pieces (units, shape checking, ranges) don't necessarily compose together easily because they end up as 3 separate libraries or something.
At work, I find type hints useful as basically enforced documentation and as a weak sort of test, but few type systems offer decent basic support for the sort of things you would need to do type driven programming in scientific/numerical work. Things like making sure matrices have compatible dimensions, handling units, and constraining the range of a numerical variable would be a solid minimum.
I've read that F# has units, Ada and Pascal have ranges as types (my understanding is these are runtime enforced mostly), Rust will land const generics that might be useful for matrix type stuff some time soon. Does any language support all 3 of these things well together? Do you basically need fully dependent types for this?
Obviously, with discipline you can work to enforce all these things at runtime, but I'd like it if there was a language that made all 3 of these things straightforward.
There’s an interesting question of if the distributor misrepresented the deal to Mora as he claims, but from the summary it appears nothing related to that is recorded that the court finds legally relevant.