My impression from the (now deleted) text is that the phone wasn't booting or in a state where it could be factory reset, at least not without considerable effort.
It seems there's a lot of criticism here about Backblaze - about how other services do it better, etc.
I'm a current Backblaze customer, not a data hoarder, etc. If you're not using Backblaze to back up your data, what are you using? Backblaze is great for me cause all I want it to do is back up my docs, files, etc. and there's very little maintenance I have to do. Is there something out there that does it better?
I originally was on Crashplan until they killed the consumer service- my main motivation for going with Crashplan was based on 1) ability to set set deleted files to never be removed from backup sets automatically, and 2) no restriction for running the client on Windows Server. I've definitely had cases where I only realized that I had removed a file I wanted after the 30 day window that Backblaze sets for keeping deleted files. Also, I happen to run Windows Server on a couple of boxes in my house for fun and I'd like to back them up- something I can't do with the Backblaze client.
Then Crashplan killed the consumer service, leaving the Small Business service for rather more money. Recently they announced that they'll be instituting restrictions on file types and deleted file retention.
I moved to IDrive for my endpoints because of the pricing being more competitive than any other option. Their Web UI isn't as good as Crashplan, the client UI is also pretty poor, it's more difficult to figure out what the client is actually doing, and I had times when it would get stuck on files for days/weeks on large backup sets. However, it's actively developed and they've fixed some issues in recent months. It's cheap enough that it's hard to complain.
For my Windows Servers, now I use Duplicacy, which can target a few different cloud storage providers. I tried Backblaze B2 first, which was a bit expensive for me in the end when I realized how large the backup set was- after a year it would have been cheaper to build a NAS and stick it at a friends house and mirror to it. Currently I'm using Google Drive as a storage target using a Gapps for business account, as the storage limits are currently "suggestions". Though I am aware that is something that could go away eventually as well. Hopefully by then I'll be out of graduate school and able to afford a less-makeshift storage target.
That aside though, Duplicacy works pretty well if you're looking for something for larger backup sets that does a bit more than Rsync/Rclone (specifically deduplication) which can target both local and cloud backends, and has both command-line and graphical interfaces. The optional GUI for Duplicacy is pretty simple local web interface but it works.
A team getting to 100% test coverage and enforcing it feels like an application of Goodhart's Law.
When a measure becomes a target, it ceases to be a good measure.
At my last job, we required 100% code coverage for most code, and the other parts of the code (in ideality) were marked with ignores that were well-thought-through.
In practice, I ended up writing a bunch of test cases only to hit the if blocks. It didn't mean that the tests I wrote were any good. I'm still a fan of 100% test coverage, but with some leeway for what needs to be ignored, and what needs to be tested later (non-critical paths, if you have a deadline, perhaps)
It gets crazy with demands for 100% test coverage, in languages where you're encouraged to write compile-time logic, macros, setup-dependent minor details, time bombs, asserts which throw compiler errors when you misconfigure, etc.
I have never used the % stat as anything more than curiosity but I have certainly looked at the highlighted reports generated to see large blocks of untested code which is genuinely useful info to see.
We tried it and moved away from it. A few reasons - one is IDE support, which has been mentioned in this thread. The other was release configuration. At the time we were working on it, it was more difficult than it should have been to use env variables at runtime (rather than build time).
I'm used to the Spring Boot approach - start with having different Spring profiles for different environments, and then let your secrets come in via env vars, but doing this via Distillery at the time required some hackery - they wanted you to build a QA build and a prod build, which didn't make much sense. Maybe it's better now, but that turned me off a lot to using it.
> Maybe it's better now, but that turned me off a lot to using it.
Sorry to hear KZeillmann! For those wondering, releases - which is one of the ways you package your Elixir project for production - are part of Elixir itself since v1.9 (~2 years ago) and reading secrets from env vars is supported out of the box. Just put the relevant code in the config/runtime.exs file.
My issue with polling is that many races were well beyond the margin of error. The Senate polling in particular was bad this year.
Sara Gideon was favored to win the Maine race in the polling, because there hadn't been a single poll showing Collins in the lead since July. She lost her race by 9 points.
It's also strange to see the region makes a difference in the poll error. The polls in Minnesota were basically spot-on, but in Wisconsin (demographically very similar), the polling average was Biden +8, with one ABC news poll showing him +17, the kind of outlier result you'd expect with a +8 average. He's gonna win there by ~1 percentage point.
There's something wrong with how a lot of these pollsters determine samples, or how they judge someone's likeliness to vote.
It was both the sample (read actual reports from pollsters on how hard it is to get a sample these days... people DO NOT want to participate in polls) and an underestimate of the number of voters the Republicans would get to the polls. If your LV model is wrong you are really flying blind and for various reasons both parties activated a ton of voters this cycle so we had an electorate that no one was able to model well. The last time this large of an electorate turned out (in terms of percentage of eligible voters) they were deciding between William McKinley and William Jennings Bryan.
> It was both the sample (read actual reports from pollsters on how hard it is to get a sample these days... people DO NOT want to participate in polls) and an underestimate of the number of voters the Republicans would get to the polls.
Exactly, polling is very difficult, and getting even more so.
I was polled a few years ago by Gallup or Pew (or one of the other well known ones). The call was from an unknown number and I took it. No way I'd do that now with all the robocalls.
Is it possible that the projections themselves affected the outcome? If people saw that they had a comfortable lead, they wouldn't be as motivated to turnout.
Then the polling results might ironically be more accurate if people believed in them less.
Yes they can affect the outcome, but the opposite direction than you described. People who feel their candidate is doomed to lose don't turn out. People like to vote for a winner.
edit: To be clear, when polls overwhelmingly suggest a landslide, it suppresses votes from both sides. But a much higher proportion of the losing side will choose not to vote, thus inflating the gap.
it's not just polls that are wrong but likely this premature projection as well, tens of thousands of provisioned and military ballots are still not counted. Recounts are still to happen in most swing states. Lawsuits are pending.
Everyone would be surprised if Trump wins, because at this point it is so mathematically improbable that even gun-shy decision desks at major news networks are able to make the call without fearing they will look like idiots. Recounts have never moved a state election more than a thousand votes that I am aware of and Trump is behind by tens of thousands in the states that matter. Lawsuits won't do anything, because no on has standing to prevent someone else from legitimately voting according to the rules in place at the time of election, nor of preventing someone else from counting those votes as legally mandated.
Elections are run by the states and so in almost all instances the federal courts will defer to the state courts when it comes to things like determination of fact. So far there has been no evidence of either fraud or misconduct and the thin claims put up so far have been laughed out of court. Lacking any claims of fraud or misconduct the only other option is to somehow be able to prove a miscount and since everyone learned their lesson with the hanging chads of the butterfly ballots this is exceedingly unlikely. With no claims to be made by anyone with standing the states are on a clock in terms of exercising their Article 2 powers.
On the first Monday after the second Wednesday in December (Dec 14) the electors are going to meet in the respective state capitals, whereupon they will cast their votes and attach six copies of their vote to six Certificates of Ascertainment which will go to the president of the Senate (Chuck Grassley), two to the national archivist (David Ferriero), and then one to their secretary of state and one to the chief justice of whatever federal district their state it in. Voila! Now at 12:01 on the 20th of January anyone, even you, could deliver the oath of office to Joe Biden and swear him in as the 46th president.
> Elections are run by the states and so in almost all instances the federal courts will defer to the state courts when it comes to things like determination of fact.
Biden is leading in most states by more votes than there are outstanding ballots; that does not really qualify as hair thin. The margin may be small in a few states, but it is large enough in a sufficient collection of states right now that while we keep counting every last vote we also know that Trump lost.
Placement. Either you want a probe thermometer measuring the internal temperature of the meat or an air temperature probe on the indirect side of grill. The gauge on the grill is likely to be off 50-100 degrees F. They're often cheaply made and not as high quality as something like a probe themometer from Thermoworks, or presumably this Weber device.
Using a meat thermometer (leave-in probe or instant) is a fantastic element of modern cooking, and a huge advancement in food safety. I can't imagine cooking without it. It doesn't mean I don't enjoy experimenting - but it does mean my chicken doesn't dry out or come out undercooked.
The temperature gauge on the lid is a terrible judge of what the actual air temperature is inside your grill. It's often low quality and not in a proper placement for your indirect heat. Depending on placement, it can be off by more than 100 degrees F
This could have been true except probably half of HN have an Android phone in their pocket. So this, like with Android and Google Play Services, is a case study in perception management. Suddenly the perception of Zoom seems to be forced in a particular direction.
My paranoid 4 glasses of wine self can believe nothing other than money being involved.
