There is actually a separate edition of the book called Modernist Cuisine at Home which is specifically tailored to home chefs who want to try out the techniques, for substantially less money than the full version. Actually, the ebook which is the topic of the article is based on the "at Home" edition, which means the price differential between the ebook and dead tree version is only about thirty bucks, not several hundred.
First of all - werd. To just about all of this.
Secondly I want to add that it's not as if there is some other definitive source that the government can use to determine the appropriate reimbursement rate for procedures. Hospitals have something called a "chargemaster list," but the prices on those lists vary wildly from hospital to hospital. And most hospitals, when quizzed as to why the prices seem so out of whack, argue that it doesn't matter because consumers "rarely" ever pay those prices.
Steven Brill had an amazing article on this subject in Time magazine, but it's now behind a paywall. You can find it here: http://www.time.com/time/magazine/article/0,9171,2136864,00.html.
And the Washington Post has a brief discussion of the article here: http://www.washingtonpost.com/blogs/wonkblog/wp/2013/02/23/steven-brills-26000-word-health-care-story-in-one-sentence/
Just to be clear: the title of this story should be interpreted "The combined traffic of Google's internet properties now account for 25% of all Internet traffic in North America."
Not, as I thought upon my first reading, "Google's mobile device software package, "Google Now", accounts for 25% of all Internet traffic in North America." That made me do a spit-take.
"The area around and to the southwest of Oklahoma City, where more tornadoes were striking Friday night, 'has perhaps the greatest frequency of tornadoes in the U.S.,' said John Snow, a professor of meteorology at the University of Oklahoma.
Hurricane season is coming.
The irony here is that I found discrete math and data structures to be far, far easier than many of my other math classes.
On the other hand, I'd already had an introduction to topics like predicate calculus. I had the feeling sometimes that the comp sci professor teaching my discrete math course didn't understand the topic much better than I did.
Put on The Evil Dead Part 2. They'll be saying it too.
They do actually address this in a couple of episodes. Part of the explanation of the retrograde technology on board the Galactica is that the Cylons were just so much better at cyberwarfare that the colonists essentially ceded that field - all computer systems were isolated so that even should one be compromised, it could not be used to stage attacks on other systems. There was a good deal of hocus-pocus involved, but at least there was an effort to explain it.
I'm sorry, my inner snarky atheist is about to chime in. Please ignore the rest of my comment if you're not in the mood.
In the study, published in the current issue of Journal of Affective Disorders, researchers comment that people with a moderate to high level of belief in a higher power do significantly better in short-term psychiatric treatment than those without.
Yeah, they could have used.... Flash. Hooray? Or Apple HLS?
The bottom line is that non DRMed content is a non-starter for them. It's not that they can't figure out how to get away from Silverlight, it's that they can't figure out where to go instead.
Do you see the obvious contradiction in what you just said? The article focuses on the birth of these Mac colo companies, which can make money in an extreme niche of the market because they're in a small group of services providers standardizing on Mac hardware. Because they have stayed almost identical between model years, the provider can just by them by the truckloads as little commodity services, knowing that if one goes that they can just swap another one in.
The in house IT department, which you like to deride, doesn't have that luxury. They're not going to buy a dozen Mac Minis just to support one small group which is completely wedded to one server platform. So in the end, everyone is happy: the colo companies get their niche business, the fledgling web business gets their preferred platform, the data center admins get to stick with their core competencies, and schmucks who have never had to run a large data center get to call them assholes. Everyone wins.
Depending on your relationship with your coworker, you could try something like this:
"Dude! What the fuck is with this? This whole module reads like it was written by David Foster Wallace after sustaining a concussion!"
Then, having gently broached your general concern, you could offer a few helpful suggestions. "How about actual English names for some of your variables, instead of packing everything into a global array called "Stuff"?"
I'm actually only half kidding here. I'm lucky enough to work with guys with a sense of humor, so when one of us screws something up we expect a certain amount of ball-busting. I really do feel that this is a valuable practice, so long as the critics don't go too far with it and the critiqued can keep a good sense of humor.
I have spent the last four years championing an initiative within Google called the "Grok Project", one that will at some point burst beyond our big walled garden and into your world. The project's sole purpose in life is to bring toolchain feature parity to all languages, all clients, all build systems, and all platforms. (Some technical details follow; feel free to skip to the next section heading...) My project is accomplishing this lofty and almost insanely ambitious goal through the (A) normative, language-neutral, cross-language definitions of, and (B) subsequent standardization of, several distinct parts of the toolchain: (I) compiler and interpreter Intermediate Representations and metadata, (II) editor-client-to-server protocols, (III) source code indexing, analysis and query languages, and (IV) fine-grained dependency specifications at the level of build systems, source files, and code symbols.
There's a bit more, but that's the gist.
Or even worse, programmers who use the Visual Studio C#
.NET WPF paradigm at work, and then use a Linux desktop coding open source at home. Probably so.
You found me.