When I saw your comment I figured I should check and see and it looks like they dropped the location permission.
https://play.google.com/store/apps/details?id=com.philips.cd...
When I saw your comment I figured I should check and see and it looks like they dropped the location permission.
https://play.google.com/store/apps/details?id=com.philips.cd...
They may save you a bit of time initially but when your company gets bigger, the ORMs will become a bottleneck.
For example I've encountered queries that are not only slow, but they generate several hundred megabytes of output all of which is sent to the user's web browser where JavaScript selects the relevant two kilobytes of data to show the user.
The worst I've ever seen was a system where every single write to the database would be sent to every single web browser viewing certain webpages. 99.999999% of the writes were completely irrelevant and javascript in the browser would simply disregard them. The server load was immense... and eventually our Sysadmin brought it to someone's attention. Where we found out it was leaking sensitive data.
OP: this is important. There are a million tools to generate PDF files, most of them don't produce nice looking PDFs.
I wonder if you could capture that energy and use it to generate thrust.
Most of the energy is coming from your thrust so it'd be a lossy process however if you're able to capture all of the energy then there won't be anything left to damage the ship.
This isn't about the 737-MAX, it's about a new sub-model which currently only exists as a prototype and is undergoing a lengthy test and certification process.
AFAIK it's scheduled to start passenger flights end of this year or year early next year and this specific issue might have no impact on that.
Surely it ought to be: pay back all 10 million, PLUS compensation to the people from who you illegally got money, PLUS a fine, PLUS holding the actual people making the decision (because surprise, a company is just actual real people doing stuff) at the very least financially accountable.
If you look at the version history of any software, you'll find it's full of bug fixes. Writing software without bugs is literally impossible. It's incredibly complex and written by "actual real people" and that means there will be mistakes.
If those mistakes lead to millions in liability, then you're going to have to start paying me those millions upfront, before I write a single line of code.
It's the same with a CEO - if people are criminally liable for mistakes made by people working under them... then nobody's ever going to accept a job where they delegate work to other people.
The solution to this issue is not to attack people who made a mistake. It's to put systems in place where you check for mistakes. I guarantee you the jury and courts that found these people guilty were presented with "facts" such as "nobody else can remotely access the software" which, it turns out, were total bullshit. The people who presented those facts in court are the ones to blame for this. They clearly either lied or made assumptions.
Both of those are serious crimes. You don't say anything in court unless you actually know it yourself. If someone else tells you something is true, you don't repeat what they said. You bring those people in as an expert witness to talk to the judge/jury directly, under oath, and you tell them not to make any assumptions either.
There should have been millions spent on a full code audit done checking for bugs in the software before allowing it to be admitted as evidence in court.
I'd loved to have been a fly on the wall of the meetings where how much money to spend on reducing ignition risk was dickered out.
Sure, it's a bit annoying for the fire fighters who turn up 20 minutes later... but I think even they would rather arrive to find a burning car if it means the people who were in that car are safely watching from a distance.
There are other horrors in the link.
I semi-regularly fix a serious data loss bug that has been fixed with an alter table query. Maybe converting VARCHAR to TEXT or INT to BIGINT... of course it doesn't really "fix" your problem, because the data has already been lost/truncated.
What's a real world situation where completely the wrong type could be written to a column? Especially in modern software with good type safety checks/etc to ensure you don't have malicious data inserted into your database? If I ever did have that happen... at least the data hasn't been lost. You can run a simple script to clean up the "horrific" data.
Everything about this paragraph is confusing:
"The researchers managed to fashion 5 meters of rope in about 10 minutes with their replica batons. For fiber, they used everything from flax and hemp to cattail reeds—all plants that would have grown near the Hohle Fels and Geissenklösterle caves 30,000 years ago. The ropes proved capable of supporting the weight of one of the team’s larger members. Reeds made the strongest rope fiber."
Reeds make very poor quality rope without a lot of processing, and even then the fibers are very weak. In contrast, flax and hemp fibers are exceptionally strong. 5 meters of rope in 10 minutes would be a very crude rope indeed, unless they had a winding rig and all of the fibers ready to go. Cattail makes good rope, but like reed it requires quite a bit of processing because it's so fleshy.
Having said that... the tool does look like it could be used for processing and weaving fibres together.
As for "making a rope in 10 minutes"... why would anyone do that? A good rope is a multi-purpose tool that can last a very long time. You'd invest days in it, not minutes.