The issue of the headline figure not capturing certain key features is mentioned as nauseum on CNBC a or any decent financial news source.
Gallup and the person who posted this is trying to make it sound like a revelation. Further almost all types of employment has improved.
Here in the UK we have a similar obfuscation technique where the opposition says more women are out of work than ever, whereas the government says more women are in work than ever. Both are true, but behind the scenes it is because there is the largest population of work aged women ever.
I'm sorry, but I do exactly what you say is impossible.
> Putting backups into the cloud is a terrible idea
> and transferring large data collection over a
> residential Internet connection makes little sense.
I work with video, music and large images. So my home backup is 3.6 TB. I now use CrashPlan: a cloud backup, who have no problem with the capacity. It took ~ 6 months to store everything, but now it just sends the deltas quietly behind the scenes.
I lost a 1TB drive the other day, and the restore worked well after a bit of jiggerypokery.
Previously I used an LTO2 tape system involving Bacula, a VMWare linux instance and a lot of changing tapes. Cloud backup is so much better
I have to admit that I don't know a thing about TPM. Like is it also available in virtual environments like AWS is providing? How could this be automated? You don't want to enter a passphrase every time a server (re)boots.
Would love to hear if anybody successfully used that.
I'm no Amazon EC2 expert, but a quick google exposed a few keen souls who tried to use vTPM and failed. This would suggest that Amazon does not yet support vTPM.
Well, unless the machine is permissioned by default you will need to give a fresh instance new authorization. Permissioning by default is the same security problem you're trying to avoid though... just shifted. Your overall goal is to have the credentials inaccessible to sniffing, right ?
I guess you could set up some form of ssh-agent handshake to make the process less manual.
Not quite a work freeze. There is a subtle difference in that only the most critical code fixes will go in, we'd just document everything else and come up with solutions for the rest.
So this isn't exactly a 100% code freeze. There are still critical fixes that might go in with managerial understanding and approval.
The downside is people then start saying things like "my fix doesn't require any code changes, only SQL changes." I am not trying to be pedantic and say SQL is code, which it is, Rather, if the change could be done better in C# but we do a workaround in the database layer, that isn't exactly ideal.
Most programmers are barely capable Stack Overflow copy'n'paste merchants.
Programmers value the hacky over the elegant, and work hard to tight release cycles.
And yet there are programmers who care, and who seek out and use better ways of doing things, including the tools to help them. Just as there are journalists who care about getting things right, digging up and exposing the truth.
In fact, a great way to lift the general standard is to make the right way of doing something also the easy way of doing it: better tools can counteract short deadlines and occasional lapses of discipline.
>Journalists value the sensational over the factual, and work hard (true) to tight deadlines.
No, people do. There are tons of highly professional journalists who want to do good work and write important, well-crafted, accurate stories. Who were inspired to get into the field by Watergate. Who are constantly begging their bosses to do labor-intensive features.
The economic reality is that there are not enough people who want this enough to fund it, except barely at a handful of institutions like NYTimes. Good work takes time and manpower and it doesn't sell. If management is doing its job (maximize shareholder value) then it is doing everything it can to turn its paper into Buzzfeed.
There are thousands of journalists who left their dying papers because they couldn't stand it anymore. Thousands more who were simply laid off, or took buyouts because they saw that they were going to be laid off if they didn't. My dad is one of these. They'd want nothing more than to work at a real paper again, but there aren't really real papers anymore.
Being sloppy and fast is absolutely about service to the customer. With a daily publication deadline, you can generally take the time to do it right. But the readership (and therefore management) wants stories on the internet as quickly as possible. Of course they are going to be sloppy.
(I agree with all your complaints about TV news, because that's what it's always been. In print... that's what they were forced to become when the money became tight.)
I guess it's relevant because the OP is saying that they wouldn't use it because they think that facts are irrelevant.
Definitely, we'd have to look at the studies in this space, namely whether journalists cite their facts, or write their pieces using citable studies/facts, etc. So I also won't accept the OP's statement of it as fact.
Though, in my, supposedly biased, opinion I'd say journalists are quite adept at twisting facts to suit their points, and also of omitting (i.e. cherry picking) facts that support their views/points.
Hold on, you're using the fact that UK journalists ironically recycle a term that's normally used in a perjorative sense as justification for stereotyping them? What you've said can be effectively applied to any possible occupation in any field.