skysight-inc/HackerNews huggingface dataset:
Biases and heuristics are the same thing.

The banana example for marginal thinking contradicts the expected value text. Expected value really only works that way for things that you expect to keep happening.

The efficient market hypothesis doesn't quite hold in the real world, but it's still a useful heuristic.

The typical mind fallacy is a special case of availability bias.

Aumann's agreement theorem assumes that both agents have the same set of goals and values. This doesn't entirely hold for humans.

Against chesterton's fence, there's also the principle that it's easier to ask forgiveness rather than permission. Or if you don't know what the fence is for, take it down and watch what happens.

I seem to recall hearing that the Hawthorne Effect could just as well be that people are more productive at the beginning of the week. Productivity experiments should not be on a weekly schedule.
> it's perfectly reasonable to have entries for popular anime shows, but we don't need hundreds of stub pages for every character in the show

You know what grinds my gears? Pages upon pages of 'useless'[1] anime guest-characters, and yet when I tried to add pages for real-life artistes from my (3rd world) country, I had the pages deleted for "lack of notability". This must have happened a decade ago, but I told myself "never again". Now I ignore Wikipedia's pleas for content under their "Wikipedia loves X" campaigns because I know they don't mean it. I doubt Wikipedia's cultural bias can ever be cured with the current editorial structures.

1. Useless to me! This is very much tongue-in-cheek
I love the simplicity. Overall, a fantastic product.
Implicit arguments are still arguments. It is just syntactic sugar, and I think syntax changes cannot change a functional language into a non-functional one.
This seems so true. Another thing I've seen employed is the idea that constantly "improving" the product is necessary. I'm not sure if that's born out of fear of not being relevant anymore "when there's all these sweet websites that play hovering videos" or whatever the latest thing some product manager saw when (s)he was trying to figure out how to look like (s)he should still have a job, or what.
Expect something soon from Deepmind

http://recode.net/2015/11/20/go-is-the-game-machines-cant-be...
Previous submission:
https://news.ycombinator.com/item?id=10807039
The important point is that the outsider's comment "synchronizes" the islander's information.
On Day 2, say you are a blue eyed person. You can see two other blue eyed people. Since these two people don't commit suicide during that day, you know there must be three blue eyed people with one of them being you.

So now you know your eye color.
Handy hint at UK airports. When there's a queue for UK passport holders, and a queue for everyone else, UK passport holders can use either queue. I went to the empty "everyone else" queue by accident and the guy said they don't mind me using the wrong queue to save time. That was 10 years ago, might have changed.
I have no feelings of transphobia whatsoever and it's only within the past year or so that I learned that "tranny" is offensive. This is not me saying that his comment wasn't transphobic (because how would I know? but you certainly would)

I'm merely lamenting my past ignorance.
"Consider a syntax with no redundancy: Any random sequence of characters would then be a valid program. No error messages are even possible. A good syntax needs redundancy in order to diagnose errors and give good error messages." - Walter Bright, creator of D language (http://www.drdobbs.com/architecture-and-design/so-you-want-t...)
For a kind of boring CRUD application you've got two major framwork issues: server and ORM. Node has a pretty vibrant bunch of app server libraries to choose from, ranging from simple but broadly-used (express) to highly-optimized and well-supported (hapi) to pretty esoteric (koa). There are others as well, but those three frameworks all get the job done exposing routes, templating HTML, and dealing with middleware-style abstraction layers to hook in your business logic. Personally, I dig hapi.js.

The problem with the node.js ecosystem that I see is in the ORM world. There exist ORM frameworks (waterline, bookshelf, etc), but they're a bit less actively-supported, a bit more kludgy, and that area is (subjectively to me) more likely to be a pain point. When I have issues on the back end, I end up having to write some custom SQL to fix them (which is easy enough, but hardly elegant). I rarely have framework-level problems with the stuff hapi.js is in charge of. As an example, I typically use bookshelf as a starting point for ORM stuff, but rolled my own hasmany and migrations code because I was unsatisfied with what bookshelf provided. Not a big deal, but also not standardized. I guess that may be one reason people end up using mongo - mongoose is a pretty handy library. I prefer postgres, so I'm stuck with my hybrid of raw SQL extending more generic ORM models.

I previewed sails.js a while ago when I was jumping into node from RoR (mainly so I could live in the dangerous world of websockets), and it was the all-in-one, monolithic nature of the framework that I found off-putting. Sails at the time didn't support hmabtm relationships at all, and it was going to be pretty difficult to lever in the business logic I needed to support on the back end (view permissions on both sides of the join). I ended up enjoying the decoupled app / orm framework model, since it meant I had more mix-and-match flexibility.

Ultimately, there's definitely no one true batteries included framework to do the entirety of a CRUD application in node.js (although who knows, one may emerge), but I'm enjoying the fragmentation's flipside: mix-and-match stuff, and lots of little libraries that just do one thing.
Linode has always been a great host. Sure they've had their growing pains but I've never been more happy with a virtual hosting provider, even their support. But yes, days without communication is not a good thing. Let's hope they learn from this.
If you aren't a part of FreeBSD core or the FreeBSD Foundation, then you don't know much about what's been happening at all. They haven't released any information about this publicly, and it wasn't talked about much at all on the core reports.
Ask HN: Offering dev. assistance on your projects
Hi All,

I feel my skills are stagnating so looking to work on some projects + I've been working solo for too long and it would be nice to work with someone with a different perspective and experience.

Looking to work on any stack, as long as the project is non-commercial. I could contribute to a OSS project but I'm looking for a more 1-on-1 type project experience.

Happy New Year !

tldr; Looking to assist on your personal non-commercial projects, web stacks prefered. email is on profile page.
The big problem with the EMH is how easy it is to miss what it actually means: That human behavior, when combined, is aggregating all publicly known information. So a market can have a price that is a terrible estimate in hindsight, but that's because of hidden information. Pure market speculation is betting on your own personal information being better than the information available at large. If you really have better information, you are improving the quality of the market price. In no way does it mean that going against a market price, or common sense, is asinine: It's just asinine to do so without first getting some special insight.

Another common misconception is that it requires perfectly rational market participants, when all it needs is a semblance of rationality in the aggregate: That individual mistakes happen in multiple directions. When that's the case, if people can know that the population is biased in a specific direction on average, the market adapts by providing better returns to the people betting in the opposite direction, which lets them bet harder later.

We have plenty of evidence that the EMH works in a general sense: It makes predictions after all, and they are testable. The rise of index funds is, in practice, saying that the EMH is true, and that we have so many people trying to devise the right prices of stocks that we are better off not paying them a dime, and going with their average prediction, saving ourselves the fees. And what do we see? Index fund that perform well enough that they are the biggest investors in pretty much every component in the SP500. And their share will keep growing until so much of the money is in an index that the average fund manager can beat the market by enough to make the fees worthwhile.

So I don't see how this hurts researchers and specialists: It just makes them focus on the search for novel information. It's the same when we try to create a new javascript framework, for instance: If web development has stunk for a couple of decades, what is the key insight that everyone else as missed? Without a key, novel insight, it'd all be busywork.
Did anybody in GamerGate ever criticize any male gaming journalists? Citation requested.
Hapi+Bookshelf :)
That means terrorists killing everyone on a plane (the same as everyone in the security queue) is an acceptable risk, as long as they don't crash the plane into even more people like at 9/11. So maybe we don't need airport security at all. Just have the air force ready to shoot down rogue commercial planes before they reach densely populated areas.

It happened in China. Muslim terrorists attacked hundreds of people waiting in a ticket hall. No need to go through security.
Happy New Year HN
https://news.ycombinator.com/item?id=10815741
There are no borders in the Schengen area, though.
>sites that won't let you read their robots.txt file if they don't like your user-agent string

That's hilarious. So do you use borrow a browser's user-agent or do you ignore the robots.txt?
You are missing the fact that these are a potential additional 100,000 positions. Those who leave the H1-B program for this program then free up those existing H1-B quota slots to be "reoccupied" by others. The net number goes up by the full 100,000 (or however many are awarded).

BTW, the Sessions quote is in regard to H-2 visas, not H1-B or L-1 etc. H-2 variants are primarily agricultural.
Learn to let the good guy win. Both within and outside.
> Both services offer to disable the auto-play

Twitter specifically won't disable autoplay for everything:

The option text reads:

Videos will automatically play in timelines across the Twitter website. Regardless of your video autoplay setting, video, GIFs and Vines will always autoplay in Moments.
Lua scripting with Redis
Self-posts have an inherent penalty.
Does reframing "cut out crud" to "saved $X in bandwidth" help? Or is this the kind of thing that customers / employers don't see?
V2's deep nesting recently caused trouble for us at work. We had errors where our node_modules folder was too long for Windows, due to the deep folder structure. Updating to v3 resolved the problem. Hopefully other flaws being discussed here can be worked out as npm evolves.
I use a French desktop keyboard and I've remapped left ctrl / left cmd / right cmd / right ctrl (it's a Mac) to { [ ] }. When used as modifiers they of course still perform their original function. Works like a charm, no AltGr necessary.
Most of that is irrelevant to the problem domain. Humans do a lot more with their brains than just play Go.
Its unfortunate the question was flagged. For example lets say Don Armstrong from Debian retired; he's done an excellent job at a stressful job but all jobs eventually end of course. You could look at the Debian wiki and say, OK we need to recruit qty one listmaster team member and you can use DDPO to look up a list of packages he maintained and someone needs to look after his former pkgs X Y and Z, etc. Debian carefully documents all delegations on the wiki and there's a bazillion automated tools to track. Presumably freebsd has something... something containing whatever Randi had ongoing responsibility over or was currently in process. That would certainly provide a measurable documentable level of damage (... X and Y will be delayed by an unknown period and Z is now not being looked at)
pomf.se used to have:

>Enable JavaScript you fucking autist neckbeard, it's not gonna hurt you

It always gave me a chuckle. Most of its clones still have it (e.g. pomf.cat).
Agreed NASA's funding is directly tied to the concern over war, especially with super powers. You can assume that NASA's budget will dwindle into the future, unless this fear re-emerges.
You Get What You Measure
Recommended resources for learning C++ nowadays: "Jumping into C++" by Alex Allain, "C++ Primer Plus" by Stephen Prata, and Kate Gregory's C++ courses on Pluralsight. You can get a free 3 or 6 month Pluralsight subscription by signing up for Microsoft's free Dev Essentials program.
There is a simple reason hapi, kraken etc. are built by large entities that have complex backends and are not really calling storage layer directly from node and even if they did they would not have used ORM. So they have 0 incentive to bake it in into the framework. At the other end of the spectrum are former "front-enders" lacking background to develop decent ORM :)
One possibility is humans actually have more training time in go to fine tune things than computers so far. 6 hours a day * 300 days * 5-20 years is a lot of training, but multiply that by millions of people who don't all come up with great models.

The idea being people with better heuristics end up as better players adding. So, more people effectivly adds more training time backing up the best models.

PS: This also means each player is using a different algorithm while playing.
Sounds like at least a few of those are legit concerns, if not bugs.

Like I said, I don't really know much about Sails. I was just interested in the idea that ~10 commits per month would be insinuated to be an abandoned project.
Aumann's Agreement Theorem is slightly misstated. A better statement would be: if two rational agents disagree when they both have exactly the same information, one of them must be wrong. The qualifier is crucial; very often disagreement is due to differences in information, not failure of rationality. So you should take disagreement seriously if you have reason to believe the other person has significant information that you don't.
Why cancer treatments like one Jimmy Carter used are suddenly gaining traction
It's 50% on top of initial investment and net of capital gains. But you're right - it's more or less a total fail. It was a small amount of stock, but right after I sold it I realized I probably should have just held it to see if they went public.
Paul Bloom: The Lure of Luxury
Uber Family with car seats
Seriously, did they think Tinkercad was just going to be a pile of CSS transforms?
Because Swift was designed to be easy to pick up by most programmers. And those are used to curly braces, from JavaScript, to languages that they teach in college, like Java, PHP, C, etc...
His argument doesn't really apply to programming languages, because when people talk about syntactic redundancy they are generally talking about redundancy in the context-free (or close to it) surface syntax of the language. But the actual language of acceptable programs depends on the name resolution rules and the type system, which generally can't even be expressed with a context-sensitive grammar.

In a language with a minimally redundant surface syntax you would still get an error if you use an unbound variable or call a function with arguments of the wrong type. The redundancy here helps tremendously for generating diagnostics. It's not even clear how you would eliminate it, because even determining redundancy (e.g. does a given type have a unique inhabitant modulo reduction) is undecidable in most practical settings.

Beyond that, a lot of the surface-level syntactic redundancy comes from the desire to match convention, e.g. using actual words as keywords and imitating mathematical notation.
> you know there must be three blue eyed people

Why? The visitor didn't synchronize anything. All of the villagers already knew there was at least 1 blue eyed person. Per the story, 99 or 100 depending on your perspective.
Users No Longer Need to Jailbreak Apple iOS to Load Rogue Apps
I'm the same way. Until someone loaned me a copy of Effective C++, I simply hacked code. The best practices in that book opened my mind a great deal, and really started me down the path to developing software and building systems. Now I'm the one handing junior developers my copy of the book to read, and hopefully helping them in the same way.
Not the poster and not quite what you were talking about but I was recently impressed that the new Node version of the Wordpress control panel is 126 Mb whereas the old php version including that and the rest of wordpress is 24 Mb (both unzipped). I guess the Node thing includes Node and a browser but it still seems to have quite a good bloat to functionality ratio.
You can track without JavaScript, but you can't just include a 3rd party service, you actually have to do the work.

Same thing for ads, JavaScript isn't required (especially for text ads, although few networks will let you do server side ad requests)
I'm personally averse to the whole singleton thing. What about server side rendering? You don't want the history to be shared across requests.

Most projects already have their own ways to pass dependencies (through DI or whatnot), and I can't help but feel like providing those singletons is going to end up messy.
They don't limit their idiocy to misogynistic attacks on women.
The world changes, so we are not really adapting to the same conditions that our ancestors did. Let's go for a fake example.

Imagine that there is a mutation that hands a human 20 points of IQ, but then makes said human extremely near sighted. For most of human evolution, that'd be a terrible call: Being able to see well was far, far more important than those 20 points of IQ: There are diminishing returns, of both eyesight and smarts.

But today, we are smart enough to make bad eyesight be a minor annoyance, as opposed to something crippling than it was 2000 years ago. So if smarts and myopia were to be related genetically, then today we'd be selecting for more nearsighted people, because today, being nearsighted is not a big deal, but the extra smarts are valuable. A change in the world leads to a different optimal tradeoffs. The one difference is that now, it's us selecting ourselves, and using technology to account for our genetical weaknesses: We are a bit ahead of Darwin's finches.

This is what is so amazing of the world today: We have social, behavioral selection mechanisms that work far faster than any external pressures we are facing today. Think of, for instance, of AIDS: For many years, a deadly STD, with no cure and not even treatment. Social adaptation to STDs (monogamy + condoms) and our awareness of the problem made it so that we didn't lose most of the population to it. Without rationality, we'd deal with a disease like that like mosquitos deal with pesticides: A whole lot of them die, but eventually a tiny minority has the right genes that make them resistant, and you get a new population of mosquitos, with different genetics. So by adapting technologically, our evolutionary pressures change completely.
That's certainly a reasonable concern. I hope you suggested some legal ways to keep expertise and trade secrets, like paying people better, not working them to the bone, not getting embroiled in collusion scandals; y'know, the basics.

Snark aside, I still think I made the legitimate point that whether or not there is actually a lack of supply in Silicon Valley is close to irrelevant to the comment you were replying to. Even when that is actually the case, responding by manipulating the market is still a problem.

So yes, I still think you were ignoring the broader point.
The bikeshed example is also somewhat misstated. In the original (fictional) story from the book Parkinson's Law, the issue is not that people looking at the design of a nuclear plant spend too much time looking at the bike shed design and not enough looking at things like nuclear safety. The issue is that the committee trying to decide whether various projects should be funded at all spends only about two and a half minutes in approving an expenditure of $10 million on a nuclear reactor, but spends about forty-five minutes arguing about the design of a bike shed, with the possible result of saving some $300. (They then spend an hour and a quarter arguing about whether to provide coffee for monthly meetings of the administrative staff, which amounts to a total annual expenditure of $57, and refuse to make a decision at all, directing the secretary to obtain further information so they can decide at the next meeting.)

The point being that "bikeshedding" is not (just) about what parts of a project to pay attention to, but which projects to pay attention to. Spend more time and effort paying attention to projects where there is more value at stake.
Everyone commits suicide at noon in view of everyone else. So the lowest possible number of blue eyed people go up one per day.

Here's a longer explanation:
Since people who know their eye color suicides at noon in plain sight of everyone else, we can set up induction.

If there's only one blue eyed person, they would suicide the first day at noon. Since everyone sees > 1 blue eyed people, they know this wouldn't happen. Since this doesn't happen, it's common knowledge that there is more than 1 blue eyed person. So if you only see one other blue eyed person, you must have blue eyes (but you don't know this yet because you see two blue eyed people).

On the second day, if there are only two blue eyed people, they would both suicide at noon. You see two blue eyed people. No one commits suicide because they either see two blue eyed people (if they have blue eyes) or three blue eyed people (if they don't). Now, everyone knows that there are more than two blue eyed people.

Since no one committed suicide the day before, you reason that there must be three blue eyed people, with the 2 people you see plus yourself. Thus, you know your eye color.

This is a bit long but I hope it's clear.
From the FAQ at pomf.cat:

> All filetypes but exe, scr, vbs, bat, cmd, html, htm, msi files are allowed due to malware.

Yes, scripting in html never hurt anybody...
It's sorta-kinda a good thing, implemented poorly. What's actually happening is that more things that used to serve HTML directly to the browser, are now just browser-oblivious HTTP REST-API servers. Which is good! API servers are great!

The correct thing to do, after implementing one, though, is to then make a "browser gateway" server that makes requests to your API server on the one side, and then uses that to assemble HTML served to the browser on the other side. (This is the way that e.g. WordPress blogs now work.)

What's happening instead is that the site authors are realizing that they can just get away with writing one static blob of Javascript to act as an in-browser API client for their API server, stuff that Javascript in an S3 bucket, put e.g. CloudFlare in front of it, and point the A record of their domain's apex at that CF-fronted-S3-bucket. Now requesting any page from their "website" actually downloads what's effectively a viewer app (that they don't have to think about the bandwidth costs of at all; they've pushed that entirely off to a third party), and then the viewer app starts up, looks at the URL path/query/fragment, uses it to make an API request to their server, and the response from that is then the rendered page.

Kind of ridiculous, no?

It does sort of make sense to me for sites like e.g. Twitter, where their bread-and-butter is running API servers and writing API clients that interact with those servers. The "web client" is just, then, another API client, written in Javascript and "zero-installed" into web browsers whenever they request a page from the site.

But for, say, a newspaper site, or a blogging engine? Those sites should definitely care about serving HTML directly, even if only for Googlebot's sake.