You just put your finger on the scale. All you can assume is that you're a man, not that you have a sister.
2,337 karma · joined July 7, 2008
You just put your finger on the scale. All you can assume is that you're a man, not that you have a sister.
At the root, we're always asking why some random variable ended up in a certain state. Our "interpretation" just changes where we ram that annoying random variable into our theory, which largely depends on where we're most philosophically comfortable with uncertainty showing up.
As for nonlocality, entanglement is a fundamentally nonlocal feature of quantum mechanics. There's no way to excise that from the theory, even if you can't exploit it to transmit information faster than light. I'd say calling it inherently nonlocal is entirely fair, that's a very different claim than that we can transmit information faster than light.
...which, as an aside, would not even in and of itself necessarily be problematic, closed timelike loops (for instance) are perfectly fine and good as long as you account for the fact that quantum interference will have very strong effects even at a macro scale in such geometries (the grandfather paradox gets interfered away, more or less, even if macroscopically unlikely things need to happen to end up with a reinforced consistent timeline).
In this case, I've never read the sources, so I have no idea if the complaint is valid.
This does not sound to me like they hopped on a bandwagon and wrecked working code, it sounds like they were trying to bring some fast and dirty code that they didn't like the structure of closer to a style that they were familiar with, which is reasonable.
Of course we don't know any real details, maybe the web boys really were a bunch of copypasta idiots that messed it all up - I've seen this scenario play out both ways, and the one thing that's for sure is that prototype engineers are always skeptical of work that other people do on their babies, whether they do it well or not.
Even a major revolution in database tech would maybe reduce costs, downtime, or latency by 10% or so, max. Since that sort of expense is never the dominant factor in a company's success, it will never be worth serious commercial investment. And as far as academia goes, there is research happening, it's just a slog because all the low hanging fruit has been picked and now people are just optimizing. Fields always slow down after the good stuff is discovered.
IMO AI is the only pure CS field worth studying right now, that tree has barely been touched at all. The mundane stuff like OS, databases, and languages have been studied to death, and unless an Einstein comes along, there's not going to be any serious motion unless the AI nut gets cracked first.
The human brain more or less works because of this - it overtrains on every signal it takes in, recognizing patterns that it has no statistical justification to pick out. But since it's simultaneously (over)training the process of rejecting those false patterns, it all works out okay, and it's actually far more effective than if it only made "proper" inferences from the data coming in, at least in the world we live in.
It will be interesting to see if this market provides better pricing for non-HFT participants.
Given that the only difference between this and a normal market is that a bunch of people offering to buy and/or sell at prices more favorable than the current inside bid/ask are banned from the market, I'm going to go out on a limb and say that no, it won't help pricing very much.
Or, rather, what it will do is move profits that would have gone to the HFT firms and shift them to people placing normal, non-speculative/exploitative/high-frequency limit orders.
Which means that really, there will be an arms race to figure out how to place orders that are as exploitative as possible without tripping the banhammer. The people that push the closest that limit will make the most money, but spreads will still likely be quite a bit higher than in an unfettered market if the rules have any teeth at all - long term value traders are not good at keeping spreads thin, I'd guess that in the current markets their effects on spreads are not even measurable at all, they are so insignificant...
It makes perfect sense for people to be frightened when a story is about how we screwed up the future by arrogantly pushing the limits of technology, Skynet and all that.
But there's no war here, no famine, there's not even a computer enslaving us or keeping us as pets. Just chips in people's heads helping them do what they want.
Oh, the horror...?
The problem with reading off a 30x variation (or even >10x) from Norvig's results is that it discounts the possibility that the same person might take different amounts of time for tasks (relative to the others in the group).
For instance, you might have people in the group that have already worked some variation of that problem. Or you might have some that had colds, were distracted, or just do badly on that sort of enumeration problem, but are killer at other problems. Every one of these possible discrepancies cuts away at the expected magnitude of the actual overall productivity difference between programmers, and should be accounted for.
Of course, since that difference is not what was being studied, they didn't set up the experiments to gather the data we'd need to best estimate the real productivity differences, so it's hard to say what we should conclude...I'm sure there are people that are 1/30th as productive as the best programmers, but what we'd really want to know is how typical they are, and what the overall distribution looks like. That's far less clear.
To the contrary, a very important part of science is a lot of lazy onlookers scouring what others have done and shouting "You didn't prove what you think you proved!"
Granted, it's always better when they are able to do the experiment right, but failing that, knowing that the original one was done wrong is still extremely valuable information, especially when it's a result so widely quoted.
"Well they were debugging, not programming." Because no programmers in the real world spend a significant amount of their time debugging. I'd consider that to be a significant amount of time for a programmers day.
To me, the problem with taking a study on a single round of debugging as meaningful is that debugging, overall, is a higher variance activity than writing fresh code.
Say there's a large group of exactly identical programmers, who would each take an average of 50 minutes to find a bug, but the amount of time for any individual to find a particular bug ranges uniformly from 10 to 90 minutes. If you give each of them a single bug to find, you're almost definitely going to measure "productivity ratios" that come close to the limit of 9x (with a big enough group). But all of these programmers are identical, so we damn well better not be publishing that as a result that "Programmer productivity varies at least as much as 9 to 1". We need to run more tests, or at least otherwise parse the data in some way in order to figure out what we can really conclude.
In comparison, the act of writing fresh code will usually have lower variance, because it's less of a "search through unfamiliar shit" task, so we could probably take inferences based on single trials there a tiny bit more seriously, though it still doesn't justify sweeping this issue under the rug.
I haven't read the study that we're referring to, so maybe I'm wrong, but since I know that this claim wasn't the primary focus of the paper (they apparently just noticed high internal variation within each of the two groups that they were comparing), I have a sneaking suspicion that we are talking about a single debugging task, and directly comparing the best and worst performers on that task.
FWIW, Norvig's results (http://norvig.com/java-lisp.html) are more meaningful as far as drawing distinctions between programming language productivity (though they don't distinguish whether the languages used are a cause or an effect of productivity differences), but they also cannot be directly used to prove that, for instance, some programmers are 30x more productive than others, because the variance within an individual's productivity is not accounted for.
Of course, there's some real variation in the averages that people will settle down to over the course of hundreds of debugging tasks, but an individual's productivity on debugging tasks varies so much that I'd be hard pressed to say much at all about the individuals until I'd seen them do at least a few trials.
It may be the case that the differences in the average times people take do end up being on the order of 10x or more, but it would take a lot of observation to say that for sure (exactly how much depends on what sort of distributions we see when we measure this stuff).
If you think that's illogical, I'd ask you to consider why a teacher is more likely to accept the excuse "my dog ate my homework" than "aliens kidnapped me and stole it". You seem to be arguing that given that the evidences are equal (a mere statement from a kid), the teacher should properly consider both occurrences to be equally likely.
In this case, I'd have to say that it's probably well deserved cynicism, though. An extremely effective first filter when any scientific or mathematical discovery is announced is to ask, "Does it look like science?", where "it" refers to whatever materials have been released.
In this case, the announcement does not look much like most science, and in fact the design reminds me more of all of those "Einstein was wrong, here's the real special theory of relativity!" sites than anything else.
This might not be a 100% correct filter, but I can't think of the last scientific breakthrough where the author didn't bother to at least set the paper in LaTeX and throw up a preprint somewhere. These days, even most incorrect proofs and discoveries look more like science than this does.
That said, as I know nothing about this field, I'd definitely be curious to hear what an expert had to say in about the specifics of these claims, as well as the other stuff at http://www.superconductors.org - it looks very crank-y to me, but then again I have known legit scientists that suck quite badly at web design, so who knows...
I have to go further, though - that the researcher is so quick to automatically draw that line connecting two phenomena that both involve group theory as being causally related indicates, to me, that we should be skeptical even about whether the explanation of the bee behavior is correct in any detail. Sometimes when you already know what you really want to "discover", it's very easy to see connections and patterns that don't hold up very well under further scrutiny.
The "this group has something to do with bees, and it's also in QFT, ZOMG bees must read quantum fields!" line of logic is so naive (yummyfajitas explained why) that it really makes me suspicious about the whole bit of research. Scientists should keep sloppy thinking like that to themselves (analogy is a great way to guide your research efforts, and once in a while two appearances of the same group in seemingly unrelated phenomena will, in fact, be connected), and when they don't even realize that this kind of thinking is sloppy, it's not a good sign...
The question on the table, though, is whether it's worth knocking the rich person (or maybe all rich people) down from (on some "quality of life" scale) a 100 to a 99.9 in order to lift the poor people from a 10 to a 20.
If you just look at that wealth distribution, you'll realize how little the rich have to suffer in order to help the poor a huge amount. And that's even before taking into account logarithmic utility functions...for all the arguments about how taxation reduces the incentive to make money, it's oh so rare for libertarians to explain why the rich still keep trying to make money even though they derive far less utility from it due to logarithmic utility functions than they could ever lose from a modest taxation rate.
In any case, here's where most of the disagreements stem from: most people that are against redistribution are concerned with optimizing the long term dollar value of the entire economy, so they want to keep wealth in the hands of those that are good at turning it into more wealth, even if the wealth that's created doesn't benefit those people directly at all (give $1 million to Bill Gates and he won't even notice; give it to someone on welfare, and it would change their life).
People that are for redistribution are concerned with optimizing the short term utility value of the entire economy, so they'd rather put wealth in the hands of the people that would benefit from it the most rather than in the hands of the people that would create more of it.
Taken to the extreme, each of these positions is absolutely indefensible and leads to a ridiculously inefficient and/or cruel economy. So we should always summarily discard any argument that does not promote some balance between the two sides.
Sadly, it's been a long time since I've heard someone present an argument that actually supports a stable balancing point, most people just argue blindly to push in one direction or the other.
My core thesis, which I call the ―law of accelerating returns,‖ is that fundamental measures of information technology follow predictable and exponential trajectories, belying the conventional wisdom that ―you can‘t predict the future.‖ There are still many things — which project, company or technical standard will prevail in the marketplace, or when peace will come to the Middle East — that remain unpredictable, but the underlying price/performance and capacity of information is nonetheless remarkably predictable. Surprisingly, these trends are unperturbed by conditions such as war or peace and prosperity or recession.
This is such baloney.
I've written hundreds of thousands of lines of code in Algol-esque languages, and just about every last line (by which I mean > 99.9%, with possibly exceptions once in a blue moon where I accidentally hit tab before I compile or something like that, which just gets cleaned up the next time I reformat anyways...) of that was properly indented. It's just too easy not to do, and I'd fire, almost immediately, anyone that was checking in code that wasn't indented properly.
Really. Where are all these horrible developers that don't sanely indent their code? To hear the Python folks tell it, they're fucking up codebases all over the place with their carelessness, but I've never personally experienced any pain whatsoever over this. Certainly nothing that a simple CMD+i can fix...
Hell, different newline types interacting badly with version control have caused me so much more trouble than indentation, and Python's not immune to that. Nor is it immune to people's editors globally forcing tabs to spaces or vice versa.
You should be working on your product instead of futzing around with a placeholder web site that you don't actually intend anyone to see.
If you actually want to gauge customer interest and collect e-mails, then put some content on that page and worry about the presentation (and I actually think that's a really good idea). As things stand, if you won't give any real info on the page then you're just dicking around, and it won't make a bit of difference to your business whether you put up the site you have now, a text only "Under Construction" page, or a trollface with a hand drawn penis chewing on its ear. Even any e-mails that you do collect are essentially worthless because they're not targeted at all to your product, so any signups just indicate that some people will inexplicably sign up for anything at all...
I really can't see any reason to oppose such measures, unless a person wants to make sure police officers have free reign to abuse captives, or lie about what they say.
One request: if possible, please label links that go directly to Java applets. For a lot of us, opening a page with a Java applet on it involves maybe a 20% shot at crashing the browser, and even in the best case scenario, my MBP freezes up for ~30 sec while the piece of crap Java plugin gets started up.
Which I'm fine with if I'm warned, and in this case I'd click through anyways.
How do UK speakers deal with non-named entities? For example:
My family is/are going out to the movie. The class was/were getting restless.
These are common gotchas on the SAT in the US; one of their favorite tricks is using plural country names, like "The United States of America (is/are) ...", where in US English "is" is the correct version. Cheap trick that really only tests whether you've memorized ETS's stance on that particular grammar point, IMO, but that's the SAT for you...
It certainly looks like it. Maybe if Eliezer sees this he can post a link to the actual finished copy?
FWIW, though, whether finished or not there's a lot of really interesting stuff in there, definitely worth a read, even if you know/care nothing about/for decision theory.
The true line has an uncountable infinity of points on the line, and the difference between an uncountable infinity and a countable one is an uncountable infinity, so we're still way the hell off.
All you're doing is reminding us that hard core libertarians hate almost everything that government does, and that they all consider most things that governments try to do to be bad for the economy.
You can't successfully argue that a particular action is bad by falling back on the base libertarian dogma that all actions of that sort are bad, or at least you can't do it without offering at least some independent support for the base dogma. We already know that you believe it; what we're asking is why we should believe it in the context of this individual example.
There are dozens of possible responses you could give, I've come up with several myself, but frankly, I can come up with many arguments for both sides of the issue, so I'm of the mind that it's likely something we'd need to see a bit of empirical data on to be sure.
One of the few things I know for sure about econ is that first-principle-based arguments tend to be complete and utter trash whenever they measure up against real world tests.