NohatCoder

I'm not suggesting that you or I operate the ventilators, but I refuse to believe that hospitals can't get someone decently qualified to do the job. If the need arise, those 160000 ventilators will be in operation in a heartbeat. The only reason not to get more is if you believe that there won't be that many patients.

Very short guide: Put a mouthpiece on the patient, connect the mouthpiece to the tube from the ventilator, turn the ventilator on.

Longer guide: Read the manual for the specific ventilator and have fun adjusting air mixture, pump frequency, pressure, volume and other stuff. Choose one of several different models of mouthpiece, with or without tubes, depending on patient needs. Learn about different failure modes and associated alarms. Learn how to operate the pump manually in case of electronics failure. Learn how to properly clean the machine.

It isn't nothing, there are some things you can do wrong if you don't know what you are doing. But a trained medical professional should get up to speed with a crash course.

That is some bureaucratic nonsense. Setting up and maintaining a ventilator is not rocket science, you can train other staff to do that job pretty quickly.

Ancillary tasks may suffer from staff shortage, but if you need one, getting a ventilator and minimal care is a lot better than not getting a ventilator.

>Not if they come in as integers that have to be coerced at some point.

In which case you can calculate the determinant exactly with your own roll, but a library will likely force you to convert everything to doubles.

>Compare ad to bc instead of ad - bc to zero, for one.

That is the same thing, a compare instruction is basically just a subtract that doesn't write the output, so you get zero/equality in exactly the same cases. Most compilers will probably turn your code into doing just one subtract and then check the flags, no matter which version you write.

You have already got floating point inaccuracy on the input, even if the library somehow avoid inaccuracy when computing the determinant, it can't tell the reason for a zero or almost-zero arising. What is the library supposed to do? You will have to deal with the issue of either a very big numbers matrix, or no matrix at all, in any case.

This is a great example of the fallacy of believing that a library automatically solves arbitrary issues.

If you don't know how to do linear algebra, a library is unlikely to help you. Rote stuff like matrix inversion is the easy part, figuring that that is what you need is where things tend to get hairy.

1. The computation is a handful of simple arithmetic statements, there is almost nothing one can do to optimize those. The library is likely written to handle inversion of any size matrix, that means it adds a bunch of control code to be more general, but also slower for this case.

2. You are wasting effort evaluating libraries. And I wonder what you lose in compile time?

3. You are calling into a black box, and you talk about opacity, a simple comment: /* this inverses the matrix */ will deal with your perceived issue.

4. Other programmers will assume there is a pertinent reason you included yet another dependency. Wonder what it does that 5 lines of code couldn't have done (surprise: nothing!).

Just don't ever look into the crates, as long as the lid stays on the crates are perfect, no reason to believe otherwise.

Where did you get those prices? I can't find anything cheaper than $4 per TB month at both Google and Amazon.

I doubt that this is going to help much, if you could fold your way to a virus cure, surely we would have seen cures for a bunch of other common viruses.

I want a concise definition, what feature makes it so? If I can't tell what is and what isn't a thingy the whole article is pointless.

What is a material design text field?

The article seems to assume that this a well defined and well known term that needs no further introduction.

I believe that the story is similar a lot of places in the world. At least in Denmark, stories of researchers spending more time seeking grant money than doing research are not uncommon.

You are grossly misrepresenting my post, I have said nothing about whether the escaping should be applied to input or output, please edit or delete your comment.

No, escape means keep, in HTML for instance Ø would become Ø escaped, but it is still there visible, same as every other character.

A method I have generally found useful is to make a whitelist of safe characters (something like alphanumeric, comma, dot and space), and escape everything else. You might escape a bunch of stuff that technically didn't need escaping, but the method is simple, rock solid, and doesn't mangle anyone's names.

I think assholery and competence are orthogonal qualities. But normal competent people don't need to tell everyone how smart they are, so you won't usually notice them as much.

I don't know if there is truly such a thing as a 10x programmer, but I have no doubt that 0.1x programmers exist in hordes. Even people who at small scale seem competent can often end up making a complicated mess when dealing with bigger projects.

There are some levels in between, like feeding an ML algorithm recordings of human drivers and expecting it to learn how to drive from watching those.

I think car companies try to rely way too much on machine learning. You get some promising results fast, but it is all inside a black box, both verifying the correctness and changing what is wrong are almost impossible jobs.

Maybe machine learning can be used to tell the difference between a dog and a plastic bag, but you'll need some hard code to describe how to react to either.

Yep, and people have been splitting their code in all sorts of ways long before anyone called anything microservices.

I think that if the question you ask is: Should I use microservices or not? Then you have already failed. The question you should be asking is: Where should the application be split?

Nowhere, or into two unequally sized chunks, are both valid answers. If you can't split a component without resorting to weird coupling shenanigans, then don't split it.

Even if you are equal in strength, they may choose to fight you out of desperation, giving up some water is probably still preferable to the risk of a fight.

These systems all favour one specific skill over any other: Lying.

The really good question is: What are they compromising now?

We can't know for sure, but I'd wager that most quantum cryptography companies have been well greased by spy agencies who expect to be paid back in backdoors.

If the woods people have been without water for days, and you deny them water, they are probably going to kill you and take your water. Remember, your first priority when encountering other humans is to survive, sometimes the right gift may save your life.

And now you have a company incapable of evolving in any meaningful way. The company will die with its current line of products.

School and workplace is just an example of two very different merit systems. One is not inherently more right than the other.

Seems like a complicated process for maybe getting slightly more compute power. Phones are plenty fast these days, processing power is rarely a major limiting factor.

Depends on the type of issues. For instance a "module x won't boot" issue is pretty severe, and it means that there is likely a ton of new issues surfacing once you fix that. Also, for an adequately broken piece of software the number of registered issues mostly depend on how much work has been put into registering issues.