https://en.m.wikipedia.org/wiki/Blood_alcohol_content (Highest levels)
748 karma · joined September 16, 2021
https://en.m.wikipedia.org/wiki/Blood_alcohol_content (Highest levels)
For example let them save for a box of LEGO they want to have. While saving they might see something else they would like. The choice about whether to continue saving or buy someting else is very helpful to think about money.
You program must break when something is not right because shitty lasts forever.
Immutable objects are great but you need to validate them when you construct them and throw an exception when something is not right. And functions should return what you would expect.
For example, this:
function GetEntitryById(int id):Entity
{
var entity = [action to get an entity];
if(entity == null) {
throw new Exception("Entity not found");
}
return entity;
}
is better than: function GetEntitryById(int id):Entity?
{
var entity = [action to get an entity];
return entity;
}In reality sometimes access via an API is way too slow or is lacking flexibility.
And I don't get this: "(e.g. if you have multiple applications writing to your database in transactions then you're virtually guaranteed to get deadlocks)"
Isn't this why transactions exist in the first place?
But the name `long covid` is also a little misleading. A lot of virus infections can shake up your body so you will need a long time to recover. A great example is the Epstein Barr virus: very contagious and it can take months or even years to recover from it.
Personally I think wise > smart.
Maybe the difference is that being smart means that you know how to apply knowledge and being wise means when to apply knowledge.
And maybe wisdom is about a desire to learn and being smart about a desire to know.
To me this seems like a million dollar mistake.
You can see this everywhere. For example those app that generate a non existing person. A lot of times the results are great except for that one spot which makes the overall result useless.
Another example is the OptiX denoiser (NVidia). You can get very nice renders in a few seconds which speeds up the workflow. But every time it has areas with a lot of flaws. This doesn't matter when you are still working on something but for production it is useless.
ML has it's use in a lot of areas where the outcome doesn't have to be perfect. But I am still not convinced it is 'production ready'.
If the error rate is only 0.5% but the death rate of those errors is 100% I am not sure it will be justifiable.
Level 2 automated driving is defined as systems that provide steering and brake/acceleration support, as well as lane centering and adaptive cruise control.
So it is the same as in most modern cars (other brands also have 'environment awareness') but Tesla still market it as 'sit back and close your eyes' driving.
In my opinion authorization should be done at read/write level because then all layers will benefit from the same authorization security.
It seems Oso is doing just that, which is great.
In fact this is how linux/unix has been working for years. But on the internet sometimes it feels like every wheel is being reinvented. Most frameworks behave as if you would open a file in Word and then Word will decide if you are authorized to view or edit the file.