2010-02-08T18:14:13+00:00

Restaurant reviewers, anonymity, and the (non-?)wisdom of crowds

February 8, 2010/stevereads/Leave a comment

A great Boston restaurant reviewer who goes by the handle “MC Slim JB” links (via Twitter) to a [mag: Columbia Journalism Review] history of food reviewing. The review is essentially divided into three themes:

* how food reviewing tracked the expanding universe of ethnic foods available in New York City
* reviewers’ perspectives on anonymity — specifically, whether they felt obliged to remain anonymous to prevent favorable treatment by the chef
* the questionable ethical guidelines followed by today’s amateur food reviewers.

The first bullet is interesting. The second is as well, and for the record I think reviewers should always be anonymous; there’s no question in my mind on this point.

To the extent that Internet reviewers make a name for themselves and drop anonymity to get special dishes at restaurants, that’s obviously bad. The [mag: CJR] piece focuses on a few amateur reviewers who prostitute themselves in this way. For what it’s worth, I’ve never heard of any of these reviewers.

What the [mag: CJR] piece doesn’t bother to examine is what happens when *everyone is a reviewer*. When chefs only need to be on the lookout for Ruth Reichl, they can post her photo up in the kitchen and keep an eye out. But when every one of us could go on Chowhound and tear a restaurant to shreds, presumably the culinary standard always has to stay high.

Of course there are caveats here. First is that, when everyone can talk, everyone’s voice is correspondingly diminished: why should someone listen to me when there are thousands — millions? — of other people on the Internet just like me? But that just changes the point a little: chefs now have to make nice not only with the Reichls of the world, but with *the entire Internet*.

The Internet speaks with many voices, of course. What you’ll find on Chowhound is that one man’s pigsty is another man’s foodie bliss. Sometimes this reflects the quirks of the particular day the reviewer went. Other times it means that the reviewer has no taste. You have to judge on your own. Certain Internet reviewers get rated highly by their peers; MC Slim JB gets that honor on Chowhound. Does that rating mean anything? Maybe their peers are all dolts; this is certainly how I feel about highly-rated Slashdot posts (whose quality, from my once-yearly checks, has declined from even its already piss-poor station).

So you just have to decide how you like the reviewer and how you like the venue where he posts. I find that if a number of Chowhound reviewers have good things to say about a restaurant, if their tastes match up with mine, and if the reviewers sound intelligent, then I should probably check out the restaurant. Over time, who knows whether this will remain true: maybe the world at large will discover Chowhound, will fill it with “EAT THE FRIED SHRIMP AT TGI FRIDAYS IT IS TO DIE FOR LOL”-type reviews, and will therefore kill its allure. As more idiots fill up the forums, they’ll tend to promote reviews that they themselves like. And so on down the drain we’ll go. All I’m really entitled to say is that as of this moment, Chowhound is my place to go for good restaurant reviews.

The world is more complicated now. I think it’s unquestionably better. Previously, you had two or three professional voices to rely upon, and the voices of your friends; if your tastes weren’t in line with the reviewers, tough luck. Now you can find people who share your tastes and follow their recommendations. It’s a happy world.

I’ve thought of this in other contexts, too. Lots of people venerate the wine reviewer Robert Parker, the man with the million-dollar nose. He certainly knows more about wine than I ever will, and he may even be better equipped, biologically speaking, to do that job than I am. Precisely because he’s such a different a wine consumer than I am, why should I necessarily base my wine-purchasing decisions off what he says? Is it at all clear that I’ll enjoy a complicated wine as much as Parker does? I certainly don’t agree with Dave Barry’s joke, probably 20 years old at this point, that no one can tell the difference between wine and melted popsicles. At the same time, I can’t detect many of the flavors that Parker can. What he considers a superb bottle of wine may turn out to be a waste of money for me.

Another way to view Parker’s job is as a *teacher*. Here I think the possibilities are more hopeful. I may not be able to taste, as Parker did during his road-to-Damascus moment, the “main components of a Riesling.” (Or maybe I can. Not sure.) But if Parker tells me that a wine contains such-and-such flavors, I can start looking for things that I wouldn’t have thought to look for before. Drinking a wine with Parker by your side may be akin to staring at an abstract painting in a museum with an art historian by your side. It looks like a jumble until someone puts together the pieces for you.

When reading Parker on wine, or Anthony Lane on film, or Michiko Kakutani on books, the question I think we’ve always asked is whether the reviewer is similar to us. If Lane says he dislikes a film for some particular reason, we have to decide whether that reason is something we care about. If it’s not, we should find another reviewer who focuses on other things. One reviewer may not like [film: Avatar] because he thinks the story is silly; another may love it for the visuals. If you’re into visuals, maybe you should listen to the second reviewer.

None of this is rocket science, of course. But it’s worth thinking a bit about why and how we read reviewers in the first place, before we decide that the Internet is the death of professionalism.

A long weekend’s journey into Sunday evening

February 7, 2010/stevereads/Leave a comment

It was a long, stressful (but exhilarating) month at HubSpot, and everything wrapped up last week. So I was looking forward to this weekend to recharge my batteries a bit.

It didn’t quite work out that way. First of all, my body took the end of the one-month development cycle, with its stress and sleeplessness and lack of exercise and not-entirely-awesome diet, as an excuse to finally collapse. The cold started on Thursday, built a head of steam on Friday, and really pummeled me on Saturday.

I couldn’t do what I wanted on Saturday, because I had to help my lovely girlfriend move her stuff from one place to another — including beds, dressers, etc. We moved all that stuff *out* of the old place yesterday, and moved it all *in* to the new place today. Normally I’d have plenty of energy for that sort of thing, but the cold took it all out of me after a few hours of work.

I took the 1:30 train back to Cambridge and planned my relaxation. Central to it was a hot toddy. Also a bed. Other than those two things, most was negotiable.

A few hours later, and here I am: pajamas on, in bed, toddy balanced on my sternum, cats both within reach, and nothing I’ll need for the next 15 hours anywhere outside a three-foot radius. The toddy has already worked its warming magic. Life … is good.

Microsoft and its critics

February 5, 2010/stevereads/Leave a comment

There’s a very odd exchange between a former Microsoft VP and the official Microsoft blog. What’s odd is that Microsoft essentially tells the former VP that he’s right: when Microsoft says that “what matters is innovation at scale, not just innovation at speed,” what that says to me is “We take innovations that others have come up with, once we know that the market is established, and make that market bigger.”

In fact this is how I’ve heard Microsoft’s business model described. And there’s nothing wrong with Microsoft’s approach, actually. Little companies innovate; big companies scale up innovation. So that’s fine.

It’s just weird, though, that Microsoft even bothered to respond, if essentially their entire point was to affirm the truth of the op-ed. I’m 100% with Jon Gruber on this:

> Why in the world did they respond to this? And even worse, without refuting any of his claims, most especially his core premise that Microsoft is divided into dozens of bureaucratic fiefdoms that fight against each other to protect their turf?

__P.S.__: Microsoft *really* didn’t need to include a fucking smiley face in the middle of their blog post.

Speaking, as we were, of JavaScript

January 23, 2010/stevereads/Leave a comment

…I’m really enjoying jQuery. I’ve never really written JavaScript before, so I very much enjoyed writing this little thing.

Automatic memoization: cleverness to solve the wrong problem

January 23, 2010April 21, 2026/stevereads/Leave a comment

This is the first time in my career that I’ve used JavaScript extensively, so I’m trying to learn some best practices. A few people have recommended Crockford’s JavaScript: The Good Parts, so I picked it up. While skimming through it looking for something else, I ran into his description (on page 44) of using memoization (essentially, caching) to speed up the computation of certain functions.

The example people always use here — and Crockford is no exception — is the Fibonacci sequence. The shortest way to implement it is recursively. As Crockford points out, the recursive solution doesn’t scale: the number of recursive calls necessary to compute the nth Fibonacci number is proportional to the nth power of the golden ratio. (From what I can see, the constant of proportionality converges very rapidly to about 1.11803. That number must have some special name.) I’ve coded both versions up in Python; the recursive version keeps track of how many function calls it had to make.

So then Crockford’s solution, and the solution written in lots of places (Higher-Order Perl, for instance) is to use memoization: cache the results of fib(n) for smaller n, then use the cached results rather than computing those values anew when you need them later on.

This isn’t really a solution, though, as my friend Seth pointed out to me some months ago. It’s certainly clever, and languages like Perl or JavaScript make it very easy. In Perl, you can automatically memoize any of your functions with the Memoize module: just do

use Memoize;
memoize(‘fib’);

and voilà: all of your calls to fib() will be memoized from then on. Pretty cool, really. Manipulating the symbol table is kind of neat.

But this has only temporarily disguised the problem. Let’s look at the time and space requirements for all three of our fib(n) implementations:

Recursive, non-memoized: exponentially many function calls, hence exponentially many stack frames, hence exponential memory usage. Linear running time.

Recursive, memoized: linear memory usage (one cache entry for every [math: i], for [math: i] less than or equal to [math: n]). Linear running time.

Iterative, non-memoized: constant memory usage (must keep the [math: n]th, [math: (n-1)]st, and [math: (n-2)]th values of the sequence in memory at all times, but that’s it), linear running time.

By using some language cleverness, you’ve made the problem harder than you need to: memoization increases your memory usage from constant to linear, and does nothing to your running time. By thinking harder about the problem, you can improve both performance aspects and not need any clever language business.

Seth has told me for quite a long time that recursion and higher-order programming (closures and so forth) are interesting but make debugging a lot harder. His contention would probably be that you can often replace a clever recursive solution with a non-clever, easier-to-debug, better-performing one.

That said, at least some higher-order-programming tools make my life easier. In Python, I love list comprehensions:

print [x2 for x in xrange(1,11) if (x2 % 2 == 0)]

or the older-school but perhaps more familiar map() and filter():

print filter(lambda x : x % 2 == 0, map(lambda x : x**2, xrange(1,11)))

(because I favor readability over concision, in practice I would expand this into several lines: a map() line, and a filter() line, and so forth)

As I’ve mentioned, I lament the absence of first-class functions in Java. Then again, I’ve seen enough people shoot themselves (and me) in the foot with unreadable Perl or Python, using all the cleverness that the languages provide to them, that I think I’d be okay with a less expressive language that forces programmers to be really boring.

Way behind on book reviews; here are some capsules

January 22, 2010April 21, 2026/stevereads/Leave a comment

I think owing to busyness at work, limited sleep, lack of exercise and similar things, I’ve been way behind on writing book reviews. Rather than wait until I have the time to handle each of them properly, I’m going to summarize as many as I can right here.

Doug Henwood, After the New Economy
(With thanks to Henry Farrell for recommending this.) The new economy — everyone blessed with thousands of (as it turns out, worthless) stock options, everyone making money off senseless business ventures, everyone a “web designer” — is over, and we’re back to the old economy. Henwood argues convincingly that the new economy was only really lucrative for the small handful of people on top, and that most of us just continued to get screwed: the American economy got a lot better for the rich and not all that much better for the rest of us. This all avoids being a tirade, because the author combines the prose of the pamphleteer with most of the erudition of a scholar. (“Most of” here is a compliment: most people don’t read scholars, and people should read Henwood.)
Ken Auletta, Googled: The End of the World As We Know It
I’d say there are three parts to this book, woven all around one another: first, and most sizably, lots of Ken Auletta being a Google fanboy (see his onstage interview with Google’s Eric Schmidt if you want to see a man keeping just on the respectable side of fawning); second, a rather powerful chunk reminding us of just how completely the Internet has changed the world; and third, some nonsense, of the sort that drives engineers nuts, about how Google’s focus on rationalizing markets means that they may fundamentally lack wisdom.

The fanboy part I’ll ignore; I should have expected, in any book about popular technologists, that it would coo over its subject. When Auletta steps back and describes just what the Internet has wrought in only about a decade and a half, on the other hand, it’s astonishing. Craigslist killed newspaper classified ads and thereby a large chunk of newspapers’ revenue. Google is in the process of overthrowing traditional advertising. YouTube is how many of us consume television shows now, and Netflix is how we consume movies. Amazon changes how we buy books. iTunes (Napster, really) turned music digital. Google is moving into the cell-phone industry. Their acquisition of YouTube looked at the time like they were purchasing a known massive copyright-infringement platform with the intent of directly challenging intellectual-property law. And on and on. It’s breathtaking.

Now, part of what makes Google Google in all of this — part of what all of us love watching — is the rationality driving it all. We perceive — and Auletta confirms — that Google approaches any new market, asks “What should this market look like?” and immediately moves to drive out irrationalities. Advertising could be done better, so Google is doing it better. Cell-phone software sucks and doesn’t reflect the computer revolution of the 1980s; Google is building Android to fix that. They see a problem and have the resources to fix it, so they fix it.

If you’re from one side of C.P. Snow’s “Two Cultures,” and you’re a writer who needs to provoke controversy in a book about Google, you will wag the disciplinary finger at Google here and bemoan their “cold, logical rationality.” It’s a staple of the genre, and I can’t really fault Auletta for it: in writing a book about a tech company, you’re either going to fall into fanboydom or into These Guys Really Should Have Got A Degree In Anthropology So That They Could Understand How Humans Really Are territory; Auletta does both, and does both rather mildly, so I have little to complain about. But in any case, he has to get in his digs: Google’s founders are confused when EPIC objects to algorithmic monitoring of Gmail, according to Auletta because the founders view the world through hyper-rational blinders. This part of the book isn’t really believable, probably because I’m a geek. Humankind has not created very many men who both are prose stylists and who can talk to geeks in their language.

(Little sidebar from an earlier part of my life. I used to work for a startup that was all about openness when it could afford to be: that is, when the venture-capital funding hadn’t yet dried up. Every month, they’d show the company’s engineers the raw numbers and the bottom line. Then there came a point when maybe they didn’t want to share quite as many numbers with us. When pressed by the engineers in the room, this company’s founder explained, not convincingly, that we geeks would just take those numbers, overreact to them, and get scared. So this was for our own good, you see.

Turned out that the numbers were really just bad in an objective sense. By the time the company was acquired — because it had a lot of intellectual property, a lot of smart developers, and a world-famous founder — the acquirer bought it by just paying off its substantial debts.

I’ve taken some lessons from this: 1) that when openness disappears, it’s time to polish off your résumé; 2) that transparency is something that companies keep so long as it’s convenient; and 3) that geeks really do have a great built-in bullshit meter, which entirely derives from that cold, rational, objective viewpoint that Auletta scorns.)

E.L. Doctorow, Ragtime
The only novel I’ve ever encountered that has a detectable meter. On quite a few pages I read it while snapping my fingers. Check out Ta-Nehisi Coates’s excerpt to see what I mean.

The story centers on one New York family and the intense, exploding world that surrounded them: Harry Houdini escaping from damn near everything; Emma Goldman (whose Living My Life awaits me on my bookshelf) singing the virtues of anarchy and inviting policemen’s truncheons; obsessive men falling prey to the charms of glamorous film actresses; murders happening on the roof of the original Madison Square Garden; and black men resisting abuse and getting torn to shreds as punishment. In its literary skill at combining many historical personages into one fluid story, it’s like [film: Forrest Gump] for smart people. This is an exciting, captivating, rhythmic book. My only suggestion would be that you read it in one sitting: the excitement is hypnotic, but only if you’ve let yourself settle into the trance that Doctorow has built for you.

(Ragtime confirms a pattern I only started to notice when I got into Philip Roth: books by men very often feature completely unexplainable sex by their male protagonists with beautiful women. The men are often awkward nebbishes, yet they end up with curvy, sexually unslakable women. It never makes any sense, but hey: if I get into the position to write a novel, I’ll probably put my fantasies down on paper too. “Maria Romero’s raven-black locks fell around her as she collapsed breathless on the silk-covered pillow. She’d spent the previous six hours engaged in her favorite activity: ecstatic sexual congress combined with a lecture on Löwenheim-Skolem.” Get ready for it, because nerd porn is coming.)

Tom DeMarco and Timothy Lister, Peopleware: Productive Projects and Teams

There’s a lot to recommend this book, and lot to recommend avoiding it. On the plus side, the authors really are on the right of the battle to make companies enjoyable for their workers. Give all your employees windows, they say; it’s nonsense to claim that this is impossible, and hotel rooms — every last one of which has a window — supply the existence proof. And more: don’t push your employees to push crap out the door; let them know that you respect quality, and they will rise to the challenge. And still more: your teams need to “gel” (DeMarco and Lister may spell it “jell,” but I refuse). To make them gel, they need managers, but they don’t need managers to sit watching their every move. Your employees want to create great work; people want to enjoy coming to work every day, and they want to produce something that they’re proud of. Make that kind of job available to them, and the quality product will flow out of them naturally. Hence the quasi-paradoxical line: Quality is free, but you have to pay for it. Peopleware is loaded with good bits like this.

At the same time, it suffers from some annoyances. The authors seem out to sell their own consultancy, so much of the book feels like hucksterism. Just adopt practices A, B, and C, and you’ll end up with a great company. There’s certainly a selection bias: those companies that enlist DeMarco and Lister’s consulting services probably differ systematically from those that don’t — either in the negative sense that more’s broken at D&L’s clients, or in the positive sense that those clients are the more adaptable ones. D&L insist that they’ve distilled decades of experience into this book, which just makes me crave more evidence that they’ve fomented real, positive change for their clients. Then there’s the inevitable question: if you guys are so good, why haven’t you started a software company?

So expect about half this book to make you pound the desk with enthusiasm. Expect the other half to make you roll your eyes.

Frederick P. Brooks, Jr., The Mythical Man-Month: Essays on Software Engineering

Everyone in software knows this book by now. It’s most famous for Brooks’s Law: “adding manpower to a late software project makes it later.” Brooks presided over a number of massive projects at IBM in the 60s and 70s. He writes from a whole different world: the technical specs for a new operating system would fill 10 or more feet of bookshelf space; contrary to my expectations, Brooks actually seems happy about that. You just have to get the right documentation guy to write clear docs.

In some ways, Brooks’s writing sounds really antiquated; it’s written for people putting together massive software projects that take years to complete. All the rage nowadays is “agile”: get something out the door within a few weeks or months, then improve it bit by bit over time. In part this is to control customer expectations: put something concrete and limited before your users; now they have a specific reference point against which they can specify their needs, rather than building a dream world in their minds that you’ll never be able to meet. Brooks’s Law certainly applies as much in this new world as it did in the old. As do Brooks’s other maxims: software still needs a designer to impose architectural harmony on the whole.

I found his “No Silver Bullet” idea the most compelling of all: that no improvement in software technology or process would improve programmer productivity by 10x over the next decade. Brooks held out some hope for object-oriented programming, but I think his hopes — feeble as they were — have been dashed. The promise and the peril in organizations comes from, and has always come from, the people in those organizations. No amount of technology is going to solve that problem. Brooks summarizes one part of this as Conway’s Law: “Organizations which design systems are constrained to produce systems which are copies of the communications structures of these organizations.” That’s still the truest thing I’ve ever read on software-organization design.

For how much it’s discussed, I’m amazed that I still got so much out of Brooks. The Mythical Man-Month remains a must-own.

Siri Hustvedt, What I Loved
This is another book that has to be read in few sittings, I think. It’s really an unending series of heartbreaks and frozen daggers to the gut (metaphorically speaking) for the poor narrator. Having read it over many sittings and scattered sessions on the elliptical at the gym, I lost a lot of its rhythm and its beauty. The narrator is a professor at some New York university (possibly NYU, possibly Columbia — I don’t know that the book ever says), his best friend is a mixed-media artist, his best friend’s first wife is a strange, cold woman, and he’s surrounded by a cast of literal misfits. People die suddenly, others get involved in drugs, and the world just keeps dragging him along. His voice has an exhaustion to it, which Hustvedt conveys skillfully: he’s at the end of his life, looking back on one disaster after another.

Obviously I can’t really suggest such a book for what it will do to your spirits, but it’s an engaging read.

Diego Gambetta, Codes of the Underworld: How Criminals Communicate

Fascinating from start to finish. You can think of many reasons offhand why such a book would be endlessly captivating, but Gambetta will continually surprise you with the twists and turns in his subject.

Start with the obvious question: you’re a criminal, and you want to communicate with your fellow-bad guys. How do you do it? That’s intriguing on its own. If you know the other bad guy, you can vouch for him (or think you can — see “Brasco, Donnie”). If you don’t know him, you need to much more carefully apply the vetting that we use in the legit world: find someone you know who knows him, ask around about him, and so forth.

Obviously your big concern as an underworld fellow is the police. They’re constantly trying to listen in on your communications, get fellow bad guys to turn state’s evidence, and plant undercover cops in your midst.

When your organization reaches a certain level of success and infamy — think of the Mafia here — you now have a brand to protect. Rival organizations start claiming your name to strike fear into their enemies’ hearts. To avoid brand dilution, you need to make sure that only those people who are actually in the Mafia say they’re in the Mafia. Trademark law isn’t going to protect you here, so you need to enforce your own brand.

And how do your establish your bona fides as a bad guy? One intensely fascinating thread in Codes to the Underworld has to do with commitment strategies: imposing some heavy cost on yourself — some cost that absolutely no one outside the Mafia (or whichever group) would ever think of fakin. Henry Farrell, over at Crooked Timber, excerpts one amazing bit on this score:

Erefaans face is covered in tattoos. Spit on my grave is tattooed across his forehead; I hate you, Mum etched on his left cheek. The tattoos are an expression of loyalty. The men cut the emblems of their allegiance into their skin. The Number [the name of the hierarchical system in Pollsmoor prison] demands not only that you pledge your oath verbally, but that you are marked, indelibly, for life. Facial tattoos are the ultimate abandonment of all hope for a life outside.

Gambetta has spent decades studying the Italian mafia. He’s a brilliant economic naturalist, with story upon story from the world out there. He’s a gripping writer, to boot. Codes of the Underworld is one of the few works of economics that you’ll be unable to put down. This may be because it’s not recognizable, at first glance, as a work of economics. But its economic cred is pristine; it’s filled with references to the great Thomas Schelling. Highly recommended, both for those who love economics and those who love [film: The Godfather].

(I’d be remiss here if I didn’t mention, by the way, Schelling’s Micromotives and Macrobehavior. It’s an boundlessly interesting piece of work.)

One little note on Scott Brown, Martha Coakley, and health reform

January 20, 2010/stevereads/Leave a comment

This election has me more miserable than I really want to go into, so let me just say this:

Yes, Brown’s election means that a lot of filibusters down the line are possible. But what people are really flailing all around about now is that *health reform*, in particular, might be filibustered to death.

Now then. If that’s what people are actually concerned about (let me be really fucking clear that that’s what *I’m* concerned about), then we could have dodged the bullet on this long ago. Obama and Senate Democrats tried to play nice with Republicans for a long while. That failed. It led to months of delay. If we’re essentially into conference-committee territory now, we could have been in conference-committee territory months ago. By the time Scott Brown’s miserable ass got sworn into Congress, we could have long since had health reform that people aren’t embarrassed about.

Lots of people, myself included, have railed against Senate procedure causing everything to get slowed down. But the fact is that health reform was and is an unforced error. The threat of a filibuster cannot explain why Democrats took so long to get the job done.

A brief note on the ethics of Harry Reid and of his critics

January 11, 2010/stevereads/Leave a comment

It speaks to our failings as a society that Harry Reid could be pushed to resign for *saying some words* about Barack Obama, whereas the entire Republican party feels no compulsion to resign for, objectively speaking, consigning many thousands of uninsured poor people to die every year and resisting all attempts to improve the lives of the less fortunate.

It speaks to the Democratic Party’s failings that they don’t say this.

A natural total ordering for health-care expenses and outcomes?

January 10, 2010/stevereads/Leave a comment

Looking at the chart on Andy Gelman’s post about health-care expenses and outcomes, I wonder if there’s any way to put all of those data points in an order. You want to say that country A is better than country B in its health-care outcomes and expenses, and you want to be able to do that for all countries.

There’s an obvious *partial* ordering for all those countries: A’s health care is better than B’s if A’s health-care outcomes are better than B’s and if A spends less on health care. That is, if A is to the left of and above B, then A is better than B. But we’re unlikely to be so lucky that countries can be put into a line that slopes uniformly down and to the right.

If there were some widely accepted way to balance expenses and outcomes, then we could achieve a total ordering here. Let’s say, for instance, that we defined the “goodness” of a health-care system as 1/3 times its per-capita price, plus 2/3 times its health outcome. Then our two-dimensional chart would collapse into a one-dimensional line, and all countries would naturally be totally ordered. But unless I’m missing something, there’s no objective criterion for combining these two quantities.

What I’m asking, I think, mathematically, is whether there’s any natural total order on ordered pairs. Probably not, right?

__P.S.__: I wonder whether the ratio of quality to price has any claim to objectivity. One would expect, though, that the marginal gain in quality for every marginal dollar spent would decrease with the quantity of dollars. (Diminishing returns.) So if we’re not careful with this ratio, it will tend to reward those countries that spend hardly any money and have mediocre health outcomes. So I wonder whether the ratio of quality to price, limited to the set of countries with quality above a minimum threshold, would be an interesting metric. This does, however, start to get us into “how much money is an additional year of life worth?” territory, which is ethically contentious.

This particular ratio, too, depends on some possibly special features of the response function (i.e., the response of quality to increased cost). In particular, the response function probably has a positive first derivative (every extra dollar buys you *some* increase in quality) and a negative second derivative (…but the amount of extra quality attained for every dollar is decreasing). This is somewhat specialized, but decreasing returns of this sort are fairly common.

__P.P.S.__: Even without this specialization, it seems fair to say that country A’s health index is less than country B’s if they spend the same amount of money but A has lower quality.

A short history of religious wars

January 4, 2010/stevereads/Leave a comment

Coworker Dan (obviously baiting me, a Mac user, from the other side of the room): “At least it’s not a stupid *Mac*. Those suck.”

Me: “I don’t do religious wars; sorry.”

Dan: “Oh, I do. I love them. And Macs suck.”

Me: “Oh yeah? Vim versus Emacs?”

Dan: “Vim.”

Me: “Open brace on the same line versus open brace on the next line?”

Dan: “Same line.”

Me: “Good. Glad we got that out of the way.”

Steve Reads

Author: stevereads