skysight-inc/HackerNews huggingface dataset:
I tried to do the math myself about the correlation, but it seems like my statistics teachers would be disappointed[1]. What R^2 did you get compared to ARI and what with PRO?

At first sight, it does not seem significant.

My claim was about poor and rich people, and you used progressive and conservatives parties as a proxy indicator, which is not great. In USA, for example, California and New York are two of the richest states and they are progressive, while the poorest tend to be conservative.

In the "comunas" 4, 8 and 9 (Lugano, Mataderos, Soldati, Pompeya, Barracas) the party "UNION PRO" did better than "UNEN" (a.k.a.: "ARI"), and in the 12, 13, 14 (Urquiza, Belgrano, Palermo) their percentages were really close.

If anything, your statement is completely unrelated to my question.

> Actually in Congress, The Workers Party (PO) brought more users to DemocracyOS than ANY other party.

Correlation does not imply causality. One possible explanation is that both DemocracyOS and PO have a stronger impact on young people.

[1] https://docs.google.com/spreadsheets/d/1TqWBMk18bbr1TQV-Wq0a...
This is essentially the idea the computer game Archon was based on.
Apparently, that practice is still banned in some US states and counted as 'water theft'.
Piracetam/choline/caffeine stack for about six months.

Would like to do another course at some stage. Mind was massively productive and I fleshed out several ideas over the period. Also got rid of the "mind fog" that starts to creep in from around 30 years old onwards.
Um, I really know (or at least I think that I know). I don't use a computer on the Sabbath. But I live in Israel, where it ended on Saturday evening, Israel time. And I was foolish/addicted enough to check HN after Shabbat ended.

I did, however, think that it was pretty funny that American Jews who know and can weigh in on the subject were unable to participate in much of the discussion!
Hamsa – A simple data-binding and observable model
Super Fuzzy Searching on PostgreSQL
Generating specs based on the behaviour of your Rails application
The goal is to generate regression tests which capture the behaviour of your rails application. Consider regression specs which capture your routes and give you feedback about non reachable routes. A further example where generated regression specs are useful are for inconsistent validations. Consider following validation:

validates :attribute, presence: true, allow_blank: true

A simple spec like:

it {is_expected.to validate_presence_of :attribute} would fail and give you feedback as a developer that your validation is invalid.
A lot of us living in the Bay Area at the time saw a lot of dynamic research some of which through apple, etc was commercialized, some through the companies them selves. Ibm almaden and HP research had a lot going on at the time as well.
I didn't mean to use that wiki as gospel, but the book citation I linked seems to hold up. And for a concept like pass-by-value vs. pass-by-reference, I don't think it's a good idea to go and come up with your own definitions if you don't have a very good reason to do so. While I agree that computing is a still a young field, and lots of stones are still rolling, it's still important to establish some common language and models just in order to communicate ideas. This includes not overloading terms that have been clearly established by now. If you find a well-known source[1] that would disagree with the terminology as cited, I'd be happy to revise my opinion.

[1] such as Kay, Ritchie, Dijkstra, Engelbart or even Matsumoto, Van Rossum, Eich, Crockford.
I'll just put this here http://what-if.xkcd.com/23/
So, the salary is still half SF, and 2 hrs away w/ TN Seattle pays %90 SF. And cheaper housing.

LA is highway culture, SF the city is transit culture.
Tips for operating and monitoring Presto (as a Service)
Calling it "pass by value" without qualifying that, for objects, it passes the reference by value, is very confusing.
lol, i checked the link too. got me excited
I think one important thing to note is the hourglass format of most scientific papers: statement of the broad problem and general importance of the question at hand, gradually more specific identification of the current challenge/contribution, down to the methods/model and results, and then widening to look at the implications and relationship of the new findings to the rest of the field.

Where you focus on the paper depends on what you want: if you are just learning the central questions and theoretical views in the field then the beginning and end are more useful; as you gain an understanding of the field you may be more interested in the particular advances in a given paper and may devote more attention to the middle.

At least in several of the fields I read regularly (linguistics, cognitive science, NLP, and developmental psychology) there are three key paragraphs that tend to have the most useful information:
1) the abstract (duh!)
2) the last paragraph of the introduction (this usually has the most concise statement of the motivation)
3) the first paragraph of the discussion (this usually recaps whatever advances they make in a usable way; actual results sections often contain a level of detail that isn't very memorable after a few days).

Citations are shorthand for entire sets of ideas--they're a means by which whole arguments can be referred to very concisely. One of the challenges in reading a new literature is in learning what set of citations are commonly reused and how, especially because the conventionalized citation of a paper isn't necessarily what the author expected it to be known for, nor what you might take from a paper on a first reading (or any number of readings). For this reason I highly recommend reading papers with inline full citations (Chomsky, 1965) rather than numeric/ indexical citations that you have to look up [1].

Finally, mock-reviewing a paper is a fantastic way to make sure you're being honest about how much of the paper you understand. Another technique at higher grad school levels is mock-reviewing a paper from someone else's (=prominent academic's) perspective--which imposes the dual constraint of understanding the paper at hand as well as the theoretical perspective behind someone else's critique.
I've used Shaila Catherine books for guidance and instructions. It's hard to say which jhanic states exactly because I practice alone with no teachers. I would guess from first to third but not for long periods of time. I have experienced piti and after that entered 'equanimity' jhanic state, subtle but alert and content concentration.

I highly recommend the book Focused and Fearless, I haven't seen such clarity on meditation anywhere else, except maybe Buddhist texts but they can be cryptic and poorly translated.

My technique is comfortable freestyle sitting (as opposite to lotus that gives me pain and takes away from concentration) and breath counting from 1 to 10 and 10 to 1 until I reach more relaxed breathing, then I switch to counting 1-1 on inhale, 1-1 on exhale, repeat until 10 and backwards, this reduced mental activity and keeps me on a) breath at nostrils and b) concentration with counting. After 15-20 minutes I usually start hitting Jhanic states with piti coming in first and then going away to enter more subtle higher absorption.

But yeah, get the above book, I am not much of a guide, I was actually lucky to hit piti within several days of Anapanasati meditation and Jhanic states within a week. I hear that some people struggle for months.
Bottom 40% - All Federal Tax - 2013 - 5.6% of tax revenue. Bottom 60% - 16.5% [1]

A good rule of thumb is all state & local taxes paid generally work out to about 1/5th of your mortgage/rent cost. But that's also not funding the F-35. (neither are payroll taxes)

[1] - http://www.taxpolicycenter.org/numbers/displayatab.cfm?DocID...
I was under the impression (and I could be wrong) that the anti-vaccine individuals are keen to blame anything on vaccines, not just MMR.

On a side note, until we have cold-hard evidence that there is a direct link between vaccines and disease X, I am going to clump these individuals in the same group as "naturopaths", "homeopaths", "gem/magnet/chakra healing advocates", whatever. I know I exaggerate a little at this point with the names, but I really have no respect for willful unscientific beliefs. Even more so when they decide to inflict these beliefs on their innocent children.

Like these people:

http://wonkette.com/580153/paleo-chefs-baby-food-book-pulled...

http://www.bubbayumyum.com/
It's highly relevant to getting a job on a software team, but only because most teams are assembled via interviews, and verbally relating stories from your past in a face-to-face meeting is the most effective interviewing technique.

And it's relevant to a job like sales. (That's unsurprising because a job interview is actually a sales meeting.) And many management jobs do have a sales aspect -- you have to justify budgets, sell work inside the company, et cetera.

But if explaining our work to outsiders were a particularly important or routine skill for programmers, we wouldn't be so bad at it. And, on average, we are bad at it. Because our actual on-the-job communication, which we practice all the time, is largely written and asynchronous, taking place on media like Slack or Github. It relies on plenty of job-specific shared knowledge, domain experience, and jargon, and it all happens in the shadow of a job-specific shared codebase that is supposed to speak for itself -- the whole point of software is to build something that works by itself -- but is also perpetually unfinished.

There are social skills that are important to have on a software team, but it's difficult to judge them in an interview. Interviews are staged events.
Challenging a candidate to defend a resume in an interview is like asking them to do improv comedy, and selects for many of the same factors: Verbal gracefulness, comfort in the spotlight, the ability to seamlessly change the subject, and the amount of time spent in rehearsal. Good candidates rehearse their resumes. We get to write them ourselves, after all, and with practice we learn to design them with hooks that lead into our best material.
Exhaustive Sum Types in Java with a Visitor
Easy: Don't agree with it (unless you're really desperate for the job).

The amount of times when "quick thinking" and "fast-solution, now, give it, before this clock ticks!!" actually happens in day-to-day situations is ridiculously tiny. So testing for it in an interview is pointless, and I'd tell them just that.
>they're fed-up of being [...]
murdered [...] by police

Are they more likely to suffer police brutality than the average person in their community?
"I mean, at the end of the day, how could anyone really test for the real panic experienced by real passengers?"
Which includes the entire program development cost - if they'd continued production, the per-plane cost would have of course been lower.
I have a very simple idea that would help: install an electromagnetic lock in the overhead lockers. If emergency lights can work then there's a way to supply electricity to those as well. Noone will grab a bag or anything.
If only humans were robots without emotional attachments, family or a desire for happiness, applying market solutions to problems would be so easy! Being priced out of the city you grew up in because foreign investors are looking for a place to hide money safely is not good for a city in the long run, or its inhabitants. Perhaps more stringent foreign ownership rules could be applied and produces an effect that didn't require the next generation to pack up and leave for greener pastures.
Nailing the First Date: User Onboarding Best Practices [Infographic]
> nobody really wants to get to the bottom of this

Don't confuse "nobody takes my speculation and anecdotal stories seriously" with "nobody wants to get to the bottom of this."
I noticed the change, thank you.
Thank you very much for posting this, I found it very informative.

For those of you who don't want to watch the whole thing, here are a few changes to aircraft that came about because of this study:

- Distance between bulkheads (clearance in the aisles) must be at least 30" to stop bottlenecks during an evacuation

- The guide lights in the aisles (for exit markers in case of smoke)

- Crew members should take a aggressive tone when directing passengers, especially when telling them to "jump" onto the slides coming off of the aircraft.

It's interesting to think that before 1985, there hadn't been any studies on people on aircraft in smoke situations. Maybe it's specifically the density of people in passenger jets that causes issues, but you'd think the military would have done studies about smoke in airplanes prior to the 80's.

It's also interesting how much catastrophe investigation resembles bug hunting. The crash had four distinct features that made it such a disaster:

- A internal piece of the engine, a combustor can, had a crack manually repaired via welding. Since the documentation to the mechanic didn't specify the maximum crack length that could be repaired, the weld was insufficient.

- The combustor can exploded during takeoff, which broke through the wing's fuel line

- The engine lit the leaking fuel line on fire

- The fire caught a wind updraft, which engulfed the (otherwise fire-retardant) fuselage, causing poisonous smoke to fill the cabin in minutes.

If any one of the 4 issues hadn't occurred, catastrophe could have been avoided. Piecing all that together really gives new meaning to the term "cascading escalating failure".

Finally, the video mentioned how one door got stuck because the inflatable ramp failed to deploy. On modern aircraft, those ramps are no joke. If you've ever heard "Cross-check and verify" on a flight, it means to verify that the ramps (which explosively inflate) are activated [1]. The 'red strip' on a flight door means that opening said door with trigger the ramp. These things are pretty powerful and can be dangerous in their own right, if opened in the wrong situation [2].

[1] http://www.quora.com/What-do-all-the-controls-in-an-airplane...

[2] http://www.npr.org/blogs/thetwo-way/2014/06/30/326919223/eme...
Yes. We do better in the younger generation. We are building for the future and thinking the long term.

and again: only rich people believe internet is for the rich. In every slum you'll find every single kid with a huge smartphone.

As you came to realize by the end of your rant: the gap is more generational than Socio-economical. That's why this makes sense in the long term.
Let's start with the encouragement: please, please put the technical details into a blog post and publish it on HN. This is the kind of stuff I've always[tm] been interested about.

> umpteen middle-boxes on the internet who won't let it through. That's all you need to know to explain the lack of industry adoption of SCTP.

Heh, I've dealt with IPSec. You don't have to convince me on the futility of getting new protocols ("the magic number on IP header") approved for end to end delivery. :) For better or worse, UDP encapsulation is the sensible thing.

I used SCTP as a fairly well known example of a protocol that has many of the modern technical requirements built in. As far as protocol features go, it is a pretty good yardstick.

Now, as for "turnkey service"... I would guess you're positing yourself as the platform provider. You need to control the server endpoints to work with multi-homing; you'll have to provide and maintain the mobile app libraries, along with best practices documentation and aids for debugging; you probably want to provide a patch for wireshark (dissector); and then there's the security to think about. That's just off the top of my head.

I am genuinely interested how you have solved the problems and where you have looked for inspiration. Because this is aimed at mobile developers, unreliable latency will be a major factor. That's something you do not have control over - maybe the protocol library can help a bit, and multi-homing already mandates graceful handling of concurrent retransmits. But mobile networks are not just unreliable, they are all too often outright crappy.

Can one ever work around that?
It seems that "high quality audio solution", in their case polycom, in our case mumble + good mics and "no videoconferencing" are among the most common thing I see in successful remote work setups.

For reasons I can't seem to put down on paper, remote setups that insist on lots of video conferences feel... oppressive in a way that working next to someone simply doesn't.
A great challenge we face is precisely this. Today DemocracyOS is strong at a local city-level. We don't believe we are ready for Federal level yet as we must understand how checks and balances work at this scale.
Volcanic eruption ruled out as the cause for Neanderthal extinction
I would say the whole point of software is to build something that people can use. If someone builds a module, but can't tell me how to use it, it's not of much use to me.

Oh, but surely they'll write documentation? Programmers, by and large, seem to suck at that too, which is why we have tech writers. But somebody still needs to explain to the tech writer what's happening! And only a few companies seem to carry tech writers for internal only products.

To put it simply, if I ask somebody how their code works and they say "Go away for an hour while I write documents" I think I'd rather not work with them. Or worse, they ask me for help debugging but can't tell me what they're trying to do. No thank you.
That time was 10 years ago. The government has no reason to put such legislation in place, because it lives off taxes on empty buildings and because it would crash the f#ck out of RE market if they turn their back on Chinese money and it starts flowing out.
Canada is huge but the nice livable places are few and far between.
This is basically what Warren Buffett does w/r/t Berkshire's portfolio cos. Though he invests less in frothy times and more in times of pessimism. But he's bottoms up too.
It seems clear to me that these practices leverage a monopoly in one market, search, to compete unfairly in another market, that is ratings and local reviews.

The actual laws are more involved, including legal theories like "tying" that I can't claim to understand (and I suspect most here can't either) but this looks no different than what Microsoft was accused of doing, which was portrayed as leveraging a desktop OS monopoly to compete in the browser market (as silly as that sounds today).
This. I recently got asked a definition question. Oddly enough, one I researched prior: Polymorphism and Inheritance.

Short of quoting a single book's definition of them, word-by-word, you'll find hundreds of different definitions of those two terms online.

So, definitions are bad, rather ask for an "understanding" or "explanation" of the interviewee.
Because they also flip these properties on regular basis (anywhere from 3 to 24 months) and it's significantly harder to do that with people living in.
Storically, python devs says the python language use "pass-by-name"
It depends on your language(s) of choice, but I prefer to use some form of linux. My go to lately has been Linux Mint.

If you enjoy windows for your day to day business, then just code inside of a linux virtual box.
There are plenty of 30+ developers with families in our organization, and all of them have projects, hacks, or ideas of their own. I would argue that this is part of the culture we have. If someone comes to an interview and can't show any past code at all, that's a worrying sign.

On the other hand, we've also hired people that have not much happening with their public github profile. We still ask to see code they might have worked on (job-related). If they can't show that, we try to have them pair with us on something simple. We have hired people in this situation, but I'm sure we've missed others that may have worked out.

If a young Carmack came through our interview process, I'm pretty sure our team would recognize his talents when asking him to go through someone else's code.
Just had this epiphany: DemocracyOS's name is intrinsically democratic.
Is this phenomenon observable in cultures that are generally accepted as more progressively feminist than the US? (e.g. northern European countries, Germany, etc)

I'm not American and I don't know much about feminism, so for me it's hard to tell the proportions with which these ideas come from US culture vs feminism (there are accounts of UK based initiatives, but there is heavy cross pollination between the US and UK student worlds).
Rant? Do you really consider I was ranting at any point?

I think I've exhibit thoughts, tried to look for mathematical proof, quoted people who are smarter than me, wonder about known problems when making decisions, and you consider that a rant?

You have no addressed a single concern I have shared. You don't have to, but your replies are infuriating because you are missing the point every time.

You are just repeating marketing phrases like "every single kid with a huge smartphone". Well, what does that prove? Does it prove that internet has as much penetration in lower income population than it does in high income one? I think not. And if you keep repeating that you are just insulting the young people who live in a slum and do not have smartphone, because you are blaming them for not having one.

> the gap is more generational than Socio-economical

That gap is not related to democracyOS but to technology. You will have a stronger impact on a young generation not because "you are thinking in long term" but because they'll understand it faster.

This comment was mostly a rant. And from now on I'll refuse to answer any comment you write until you want to provide something useful to talk about, or even back your statements.
Both could be right. You might not have had the skills they were looking for, but could build a successful company (lead generation isn't algorithm intensive, is it?). I've seen exactly that happen more than once. Shipping something and running the business matters far more in many cases because the technical challenge in most companies is very little.
Unfortunately, there's a real professional risk in speaking out against this tide of censorship, so I won't say much.

This is a great essay on the increasingly anti-controversy left: http://slatestarcodex.com/2014/04/22/right-is-the-new-left/
Creating a safe space seems very reasonable, but I'm not sure I agree that the implication is that the remaining space is therefore fundamentally "unsafe." Emotional topics can definitely benefit from intellectual discussion, but it is not unreasonable to say that a portion of the population may very well not want to be a part of it
I hope you would promote your contributions when applying for a job, it definitely makes a difference. Looking at a public profile is not everything, you're right.
5 superb golf hotels in the world
Better yet, learn to use Vagrant. I used to code in a VM until I found Vagrant (which is still a VM...but "headless"). It uses fewer system resources, is faster to spin up new machines, and has great documentation.
It just proves that you have never been in a slum from Buenos Aires. And yes, denying a rant with a rant speaks for itself. :)
Cheap flights to Singapore
“So many people spend their working lives doing jobs they think are unnecessary”
I think intelligent HN readers are starting to just skip these racist/entitlement based real estate posts.

I hope.