392 karma · joined February 13, 2010
In any case, even the standard you're trying to apply is ridiculous. People at Google or Facebook might believe that their puzzle-solving interview process ensures that they get only the best employees (how ego-gratifying such a belief must be) but I also know dozens of people who've gone to Google so I know better. On average those people are pretty good, probably even a little better than the Red Hat average, but only a little. By the standard of actual talent that's acquired, Red Hat does just fine. It's simply not true that "nearly all" of the talent goes to any three or four companies, no matter how big or prestigious. The Red Hat contribution to the Linux kernel alone shows that they can match or exceed anyone when it comes to talent in some areas.
In fairness, I should point out that it's not all daisies and starlight at Red Hat either. It's a billion-dollar global company. Yes, they (we) hire quite a few people in other parts of the world, because - believe it or not - engineering talent is not an exclusively US trait. Like any company we try to get the best bang for the buck, and sometimes that means hiring elsewhere. It's not Red Hat's fault that wage scales in the US are unrealistically high. When you have the ability to coordinate teams in many locations, and talent is available in many locations, you take advantage of it. This can be difficult to deal with as an employee, as can the fact that the average level of social ability at Red Hat seems a bit lower than average, but it's not an issue of low technical ability as you portray it.
Are you seriously suggesting that standardized tests are the only way to measure school or student performance? What about non-standardized tests showing improvement within the same region or district? What about measuring achievement differences after leaving school? There are plenty of other options besides standardized tests.
In addition to cherry-picking and strawman, you've just added the the excluded middle to your list of fallacies. There are more than two options here, not just standardized tests or mere guesswork. Just because something can't be measured by one yardstick, even if it's the most accurate one (which itself is debatable in this case), doesn't mean other yardsticks won't suffice. Do you really want to turn this into a discussion about intellectual honesty? I'd relish the opportunity to cast your disreputable claims and tactics even further into oblivion.
Of course you will, even though - or perhaps because - the intermediate result is far more inflammatory than informative.
"Because the Finns don't do standardized tests"
The fact that they don't do standardized tests doesn't mean it's impossible to know whether they're doing better. They embarked on these reforms because of a perceived problem, and seem quite satisfied with the results. If educators and researchers believe there has been improvement, based on other evidence, then I'm disinclined to second-guess them based on one semi-informed and heavily biased blogger's commentary.
Of course, treating ethnicity - and particularly just white vs. non-white - as the only variable other than the educational system itself is itself offensive. One might also consider the effects that 300+ years of distinctly US culture and history have had on attitudes toward education, teachers, or the relative social/economic priority accorded to either. Or the effects that wealth distribution within the US or wealth differences between the US and other nations might have. The US student body is simply not the same as the Finnish one, so if Sanandaji really wanted to isolate the effect of the educational system then he'd have to adjust for more than one other variable.
Alternatively, he or you might take note of the fact that the current Finnish results are the result of change to the system while holding demographics relatively constant. What works in Finland might not work in the US for all sorts of reasons, but claiming that it won't work specifically because of ethnic makeup is both intellectually and morally dubious.
By way of supposed refutation, you present a source that is full of strong claims substantiated by little more than the most blatant cherry-picking. The author's "correcting for demography" is no more than throwing out the data he doesn't like. Ignoring the fact that the immigrant factor has already been examined, he pulls tricks like comparing second- and third-generation immigrants in Finland to native Swedes. Notice how the obvious comparison between native Finns and native Swedes isn't made, because it wouldn't support his conclusions. Then he goes on to say "In the case of America, 99% of the population originates from other countries" and suggests that we compare such loosely-defined American immigrants to people in their home countries - without regard for such things as economic differences between the countries. After arbitrarily excluding Asians because they pull the results up, Hispanics because they pull the results down, and undeclareds for no methodologically sound (or even fully explained) reason, he comes up with a highly suspect graph purportedly showing how the US "beats" most of Europe.
Here's the kicker: even after cooking the data that much, Finland still comes out well ahead of the US. No matter how hard he tries, he still can't manage to reverse the original conclusion. In the end, citing that does more to discredit your position than to support it.
[citation needed]
The problem is that, in ext3, not using data=ordered is also problematic - this time in terms of potential corruption and security issues. That's why even the people who brought you ext3 abandoned it years ago in favor of making ext4 do these things the right way. If you want reasonable fsync behavior, plus niceties like block-size awareness and trim/discard support, you need to use a modern filesystem.
A piece of software that embodies a broken approach to a solved problem is by definition obsolete, and that includes ext3. Please don't make claims about what's obsolete when you don't even understand the issues that would make it so.
* When discussing "__name__ == '__main__' he complains about 13 non-alphanumeric characters, and then proposes a setuptools-based alternative that's 12 extra lines.
* He disses asyncore/asynchat, and then proposes the much more complex Twisted instead.
If your project is already big enough to have multiple files, already complex enough to require Twisted-level functionality (though even then Twisted sucks compared to Tornado or just about anything else), if it's already being packaged for general use via setuptools, then following these suggestions is almost free. OTOH, they're way overkill for other situations. About three years ago some colleagues and I wrote an asynchat-based server to coordinate certain administrative actions on a 1000-node system. It was stable, it performed as well as it needed to, and - even after working around some "infelicities" in asynchat - it was still only half as much code as would have been necessary in Perverted.
I don't think I'll be signing up for any idioms or coding standards that are based on an assumption of using Python as a direct replacement for Java. Neither should anyone else.
http://notinventedhe.re/on/2010-4-22
If you re-read the article with an eye toward how it describes the behavior of programmers even more than it describes that of business people, it becomes much more valuable.
http://news.ycombinator.com/item?id=1998819 http://news.ycombinator.org/item?id=2083997 http://news.ycombinator.com/item?id=2688984 (includes bonus downvote threat against any who disagree)
Sometimes the right thing to do when you're wronged is to let it pass, no matter how much it sticks in your craw, for strategic reasons. Sometimes giving in to that moral-outrage addiction simply does more harm than good, no matter how justified the outrage might be. And yes, I've very much been in that position myself. It sucks, but I've learned that it sucks even more to have a self-inflicted wound on top of the one I got from someone else.
I know that. What I might be able to do, though, is explain why his example might be a bad one to follow. Or maybe it's a good one, for those of the "no publicity is bad publicity" mindset. In any case, I think it's worth it to express my view. These things do affect businesses and livelihoods. Maybe it's too "meta" for some people, but - unlike some - I won't tell people who disagree that they should remain silent.
"I think this is a bad direction for our threads to go"
It's not only a bad direction for "our" threads to go; it's a bad direction for the broader discussion - across here, Twitter, various blogs, etc. - to go. That's my point. HN isn't an island. I've seen quite a few people who disable comments on their blog posts and explicitly direct readers to the corresponding post here for discussion. The real damage to real reputations is being done elsewhere, and condemning those who point it out here seems counterproductive.
"I don't think you can talk about "de-escalation""
Ad hominem, pure and simple. I'm not one of the principals here. I have nothing to do with the companies or communities involved. As a mere commentator, nothing I say affects those relationships one way or another, so de/escalation is an inoperative concept. If you want to disagree with me fine, but please stop finding new ways to tell me I shouldn't even have an opinion.
Furthermore, this kind of "reputation management" (or whatever you want to call it) really does matter, and I think there are important lessons the HN audience can take away from it. Being conciliatory toward one person or group just isn't very convincing if you're almost simultaneously trying just as hard as ever to alienate others. The mixed messages, even though they're supposedly addressed to different people, make even the conciliatory part seem insincere. If I were in Donald's or Martin's position, I'd be wondering how long the constructive tone - and the original letter was very constructive - will last before the inevitable reversion to form. The lesson is that if you want to claim the moral high ground you have to stand on it for a while. Stephen was wrong to publish what should have remained private correspondence, but calling him out like that only ensures that the controversy will continue. The urge to bare teeth and show dominance overwhelmed the rational choice to let this whole thing fade into a natural and well deserved obscurity.
What was called for was de-escalation, and anybody else who finds themselves in a similar situation (many of us have or will BTW) would do well to watch how this one plays out.
"That, @jodastephen, is a fucking announcement by Yammer about Scala." http://twitter.com/coda/status/142047850426146816
Ah, so much better than those "slapfights" we have here at HN, isn't it? Protip: backpedaling and fence-mending don't work if you go right back to the kind of public behavior that got you in trouble in the first place.
I'm not quite sure it's valid to write off SPARC as an architectural dead end when the current fastest computer in the world uses it, and the next crop of US competitors for that crown are all based on the Cell/BlueGene lineage. GPUs are also more broadly applicable than you might think. Besides video and audio processing, they can be used for many crypto-related tasks (witness their popularity for Bitcoin mining), various kinds of math relevant to data storage (e.g erasure codes or hashes for dedup), and so on. Many of their architectural features are also being copied by more general-purpose processors as core counts increase, as well.
Yes, high-end HPC is too obsessed with LINPACK. Nonetheless, it remains a good place to look when trying to predict the future of commodity servers. Even if ARM does displace x86 instead, many features besides the ISA are likely to come from HPC. Perhaps more relevantly, either outcome is still very bad for Intel.
At the high end, look at the http://top500.org/. #1 is based on SPARC VIIIfx. #10 is based on the PowerXCell 8i. #2 and #4 both derive much of their power from GPUs. Even that understates the situation, because many of the most powerful computers next year - Blue Waters, Mira, Sequoia - will also be based on non-x86 architectures. Then look at what Tilera or Adapteva are doing with many-core, what Convey is doing with FPGAs, what everyone is doing with GPUs. Intel is going to be a minority in the top ten soon, and what happens in HPC tends to filter down to servers.
So Intel has already lost mobile and HPC. Even if Intel keeps all of the desktop market, what percentage of the laptop and server markets could they afford to lose before they follow AMD? Maybe it will happen, maybe it won't, but anybody who can see beyond the "Windows and its imitators" segment of the market would recognize that as a realistic possibility.