skysight-inc/HackerNews huggingface dataset:
If you have any interest whatsoever in the product they are working on's success for example, tell them that. That's a good thing to tell them. If all you want is any job anywhere then you can probably work at Subway. If all you want is any job anywhere that pays as much as they do then at least tell them that.
The author's point meets with my own observations.

Something else I observe is that a person who works on multiple projects successfully almost always has one or more people who s/he can delegate tasks to. There is always someone on the project team, in my organization's case it's the software engineer, who cannot delegate. The tasks simply have to be performed by that person or the project fails. The person working on those tasks will not be able to work on as many projects as the project leader/initiator. Personally, I need 3 hours of uninterrupted time daily in order to push forward on a new application. To get maximum performance, I need two 3-hour blocks of time separated by one 2-hour block of time to do something unrelated.

Another point is that the author limited his scope to work. I think everyone has multiple "projects" going on at all times. They are just not all related to work. Having a family, home, hobbies, civic involvement all necessitate working on multiple "projects" simultaneously.

The people who successfully keep so many "projects" going are good at not being stressed. The author makes this point and it's a good one to reflect on.
Show HN: The best finance feeds on one page
Except she did not complain to her employer. She tweeted and made it a public issue, in a public forum, open for public discussion. The interesting legal question seems to be: Does an employee have the right to bring serious harm upon their employer as a result of an unreported, self-directed response to [perceived] sexual harassment from others [not coworkers]? And in this case, sexual harassment is quite a stretch since it was a mild joke and she was not involved in the conversation. That's a pretty big door to leave open.
The last time I've seen information and discussion about this, I've considered the viability of humans creating an artificial parasite to replace the parasites we are missing right now.
While this is interesting, I don't think starting a war to send older people to is a justifiable solution. Sending the horses to slaughter or to war are different means to the same end.
Show HN: Trip.js, a jQuery plugin for product landing page navigation
We need analytics for that now? Wow... Next, lets automate lungs to breathe.
I write a blog since 2001. So I am a known person in the design field. Over the years I have created a kind of network of readers which access anything I create or publish in my blog. That's the fastest way, and pretty healthy way to start. Then I try to open the case using paid advertising methods.
> If you want to complain, start your own framework!

God no! Not another framework!
Working doesn't necessarily stop at the end of the typical working week or even 40 hours in that case. Working hard can include renovating your own house, toiling in your own garden, cooking, cleaning, volunteering, networking, all sorts of things.
People who win the lottery often end up worse off than when they started. Giving everyone a multiple of the highest lottery winning every year would be destructive.
Microsoft Cleared of Infringing Google Patents With Xbox
AI make more mistakes than humans at some things, but only because, like humans, they are just beginning to understand. I might make similar mistakes reading articles written in German, because I am not yet fully fluent in the language. Similarly, NLP AI is currently not "fluent" in English.
If you had to compromise, what about enabling the buttons on hover? You'd still have people accidentally enabling them, but fewer than if they were auto-enabled.
The article isn't just about "disability issues". It's about perverse incentives, which certainly falls in the "intellectual curiosity" category. Also it's interesting for its description of a community that might have only 1 sit-down job!
If it is, I see how this could work out.

1) Open a website with raunchy jokes "by accident"

2) Sue them for all they are worth

3) Profit!
Are you going to do something about fields needing dependencies? So say you have a django-tinymce field in one of your migrations but remove it later, South will currently still depend on django-tinymce, even though in the database it's just a text field.
I think it is reasonably clear from the GP that relative levels of investment was the gist; of course rich people live somewhere, moves about and try to keep themselves happy.
Dealing with Hard Problems
> the RSS protocol was still dying because most people have moved on to other ways of consuming news

Any evidence to validate this claim? Popularity of Twitter or Facebook doesn't have to be at the cost of RSS. Even if it was, it doesn't make one more relevant or irrelevant. TV did not kill Radio (at least for everyone).

New applications like Pulse depend on RSS. Many users depended on Google Reader. Now they have to learn a new application. Some of them use mobile apps which are pointing to Google Reader. It is not going to be an easy change.

People are mad for a reason.
The Pirate Bay Is A Trailblazer In Technical Resilience
Repeatable, randomly ordered RSpec test runs on TeamCity
When the Whole World Has Drones
Probably because the former article feels relevant to a wider audience here than something about GCC does. There are probably more Americans than C developers on HN.
do you have any real world demos / benches etc that back you up here?
After living in China for 4 years, my allergies are gone, and while I got sick here a lot then, I have not had a serious cold in 6 years.

The allergy experience mimics many other people who spent time in Asia. The no colds - I think it's related, but most people do still get sick. I used to get terrible colds every few months my entire life. I can now scuba dive because my ears aren't constantly damaged by frequent sickness and fluids.

My theory has always been that allergies are a symptom of an under-utilized and under-exercised immune system. Our bodies are designed to be under constant attack. Much like the US is unable to resist invading countries when the world is at peace, our immune system can't stand a sterile body with no foes.
Visit new and upvote the interesting articles.

Make great posts on the threads that you enjoy.

Ignore the threads you dislike.

Flag the threads that do not belong here.

As sp332 says, some comments there are interesting and can be applied to start ups - 'be careful with incentives' is true, and incentives are a tricky problem that haven't really been solved yet. Partly because exposing the system to the public is a fuzzing that you can#t really do before launch.
I use RSS for low-traffic sporadic blogs and a handful of higher-traffic news magazines. I don't get too many items a day and it's quite easy to quickly remove the ones I'm not interested in. Then I'm left with about 1-10 interesting articles every day, which is pretty much what I want.
>>It’s not unlike the widely criticized model that Microsoft pursued in its pre-Millennium days as a monopolist: Embrace, extend, extinguish.

Ridiculous. Microsoft works to eliminate the competition, whereas Google is just not supporting it. RSS will not be eliminated due to this decision.
Then I don't see why it's important to state that those with lower incomes paying for housing, transportation or entertainment is the reason for their inability to become wealthy. Merely stating a difference in income causes the disparity is enough. Housing, transportation, communications, food and even entertainment are necessities.
Consider the law of energy conservation. I'd regard performance the same way, that is, we get closer and closer to the optimum runtime for a given problem, but can never exceed it. For example you cannot solve a NP-complete problem in polynomial time or better. Standard C++ guarantees a lot in comparison to higher-level languages. So, C++ is constrained more than i.e. Haskell. When strong AI is achieved, I'd suppose you'd be able to achieve the optimum runtime for any given problem.
The whole article makes for some pretty depressing reading, and touches upon some important points. For me, the most crucial and eye opening is the stark contrast of the relatively open ecosystem we had back in 2005 to what we have today. You can't help but feel uncomfortable about the whole direction we're taking with tightly controlled silos of information (Twitter, Facebook, G+, etc.) using extremely limited, or highly monetized, API access, when you read something like this:

"One thing that’s definitely coming (and some of these already exist, although haven’t yet been made public) is extremely deep API support. Our general plan here is to expose nearly everything in NewsGator Online via API, and allow folks to build applications that leverage our platform in unique ways."

Google is just as guilty as several other parties of bringing about the situation we have now. I get the fact that everyone is looking for ways of increasing revenue, but they're doing it at the expense of openness, instead of leveraging that openness (see RSS for example) and building services and added value on top of it.

I hope the death of Reader serves as a wake up call on several fronts.
the big pain at the moment with the MRI GC is that it stops the world, on Discourse we see a 50-60ms stall every few requests. Can totally be mitigated with unicorn and oobgc (we will move to this), still a PITA.
They will be reassigned later on
Apple and Microsoft also ship a lot of products that use H.264 and thus have to pay for their use of H.264, so I don't think it is at all obvious that is it a profit centre for them. Microsoft at least have said they lose money on it, and I doubt the situation for Apple is much different:

Though they have patents in the H.264 pool that MPEG LA licenses, Microsoft has said it pays MPEG LA twice as much in royalties to ship H.264-enabled products than it receives in royalty payments back. And Apple has only a single patent in the H.264 pool, so it appears its interests in H.264 and MPEG LA are not directly financial.

http://news.cnet.com/8301-30685_3-20038615-264.html
Setting myself on fire because of Google Reader
Goodbye cruel world.
Looks like he only did the intro. The main site credits these guys - http://www.artisanblue.com/lsg/
Here's our announcement thread as well: https://news.ycombinator.com/item?id=5406732
Is it April 1 already?

"The first discovery of this sort was made in 1851 when the workers in one of the Massachusetts mines extracted a zinc silver-incrusted vase from a block of unmined coal which dated all the way back to the Cambrian era which was approximately 500 million years ago. "
mdasen replied to that pretty well in second half of his post.
I'm sure there would be people in Yahoo would want to help, the problem is actually finding and getting in contact with someone who does care.
There is more information at the EFF page [0] linked in TFA, although not quite the same "call to action".

[0]: https://www.eff.org/deeplinks/2013/03/defend-open-web-keep-d...
AM::S maintainer here!

Conventions are more than just HTTP verbs, and the REST you refer to is... a set of conventions!

If you look at the spec for, say, ATOMpub[1], you'll find a set of conventions on top of REST: "Here's how you retrieve a resource"[2], "here's how you edit a resource"[3], "here's how you delete a resource"[4], among other things. This is because (as I'm sure you know, since you care about REST so much) that HTTP verbs do not map directly to CRUD, and there are verbs that do other things as well, so it's important to say what we mean, exactly.

"Conventions" are just putting a little bit of formalism around communication, so that both parties know what's being discussed. That's _really important_, especially between back ends and front ends. When AM::S spits out conventions-based JSON (there isn't a good name for the format yet), I can be confident that Ember apps will understand what I'm talking about, and that relieves work I'd normally have to do.

1: http://tools.ietf.org/html/rfc5023

2: http://tools.ietf.org/html/rfc5023#section-5.4.1

3: http://tools.ietf.org/html/rfc5023#section-5.4.2

4: http://tools.ietf.org/html/rfc5023#section-5.4.3
I offered to give Google my first born to keep Reader alive but they didn't even respond. First iGoogle was given a death sentence. Then Reader. If they shut down Currents or Google Print I am going to move to Canada.
This gets said a lot 'RSS is dead'. It's very much not, in terms of people consuming news through it? Maybe. But it also powers podcasts, for example, and they're going from strength to strength. Plus a lot of sites showed they still get a large amount of traffic via RSS after the announcement.

A million users isn't a lot at Google scale, but it's by no means dead.
> So I don't know what's with all this "Google killed RSS". Google didn't kill RSS. Twitter, Facebook and RSS' "geekiness" that made sure it never crossed that "chasm" into mainstream usage (and what doesn't grow will probably die, as nothing is constant) are what killed RSS.

If you ask me, it's the combination of browsers and websites not properly exposing the existence of RSS that has stunted its growth.

Firefox used to have a button for subscribing to any RSS feeds it found in a webpage in the navigation bar. It was the only browser that did it (EDIT: that I was aware of - others have pointed out Safari also had this feature for a while), and it was a fairy obscure button too. Then they removed that.

So now you actually have to hunt for the RSS feeds - and since many webpages use a gif saying "RSS" (meaning text search is useless) that isn't always easy.

It's not difficult to use at all, but it is certainly a very obscure feature of the internet. That halts adoption.
I assumed I just didn't know what the 'Monte Hall' approach was! :)
RSS is a technology, not an industry and Google's killing Reader may not necessarily kill RSS. I've switched to Feedly and love it. I wished I'd been using Feedly years ago. Reader is quite pathetic in comparison to Feedly actually. But I didn't know that. I used Reader because it was from Google and all my colleagues were using it.

As a result I'm checking out alternatives to other Google services. I've been in a Google rut for many years now and it's time to get out of it. It's all good.
> A satoshi (not satochi) is 0.00000001 BTC, not 0.000000001 BTC.

I have no idea, visually, what the difference is between those two numbers, and I so suspect no one else reading does either, without manually counting the zeros one-by-one.[0]

Here's an idea: we sometimes use commas to the left of the decimal point to make the numbers easier to read, perhaps using apostrophes to the right would also make things easier to read? E.g.:

A satoshi (not satochi) is 0.000'000'01 BTC, not 0.000'000'001 BTC.

I can easily tell the difference now. (The idea behind using apostrophes and not commas is that you won't inadvertently confuse the right-hand side of the decimal point with the left.)

Anyway, carry on. :)

[0] There's also scientific notation, but that only works in cases like this with lots of zeros between the decimal point and the number in question. With a number like Pi, scientific notation is useless.
I love using Google Reader but I don't see what the big deal is. It seems like an RSS reader is something anyone can build in a month maybe. There are alternatives that seem to be less than optimal but I assume they'll get their act in gear. I would be in their place.
What' s interesting is that this move to disability is just another manifestation of the unanswered question, "what do we do with all of these people for whom the economy no longer has use?"

Between globalization, automation/technology, and "increased productivity" (aka working people like slaves), we just don't need as many U.S. workers. Yet the wealth is still flowing, corporations are realizing record profits, and more billionaires are being minted.

We here on HN tend to feel immune, due to our skillsets. And, while it is true that the shift currently most affects those with high school educations and/or in other sectors (manufacturing), our time is coming. With continued outsourcing, gains in automation (software writing software), and other shifts, we will all experience this. While the software and technology we here produce are helping to facilitate the shift for others, some day the focus will be on us as too costly or ineffecient.

So we will have wildly profitable corporations, an extremely wealthy investor/executive class, and an economy that produces all that the world needs while employing only a tiny fraction of the world's population.

Either these entitlement programs will continue to bloat to unprecedented levels or we will require a fundamental restructuring of society.
I don't get all the fuss:
"Google Reader was born in October 2005"..."the short life and sad death of Google Reader"?

Come one, I think that 8 years is a very long time in the (online) IT world. It was pretty obvious that RSS wouldn't be something for the long-run anyway.
To me, and this is strictly from the POV as a gamer: I hate when games fail to tell a decent story. I lose interest almost immediately.

Screw visuals and focus on story. I can even accept crap gameplay if the story compels me.
It might be naive, but my own little protest is avoiding Google+ whenever possible, as a user and in projects I build.

RSS isn't dying of natural causes. Plenty of small-medium sites are getting orders of magnitude more traffic from Reader than from G+. Google and other major companies are trying to deprecate it in order to replace with their own, tightly controlled, solutions.
Let me google that for you http://speed.pypy.org
This page http://docs.angularjs.org/guide/di is a good starting point.

Angular makes extensive use of dependency injection. The unit of DI in Angular is called a provider. A provider is a function that can be injected and takes it's dependencies as arguments. The function then performs a provider role specific action when invoked.

The specific problem here is when the developer relies on Angular to infer dependencies. Angular does this by converting a function reference to a string which returns the full source of the function. It then parses the function parameter names and resolves those as dependencies.

The canonical example of this is an Angular controller (which is one of the provider roles).

someModule.controller('ControllerName', function($scope, $http) {
$http.get('/something').
success(function(response) {
$scope.someProperty = response.data;
};
});

A minimizer changes the above to something more like this:

someModule.controller('ControllerName', function(a, b) {
b.get('/something').
success(function(c) {
a.someProperty = c.data;
};
});

When angular parses that it sees a symbol named 'a' and tries to resolve that as a dependency.

As I mentioned elsewhere, everywhere Angular takes a function as a provider it also takes an array. The array is expected to be a list of dependency named and a function. I've found that the DRYest way to declare a provider is like this:

someModule.controller('ControllerName', ['$scope', '$http', function($scope, $http) {
$http.get('/something').
success(function(response) {
$scope.someProperty = response.data;
};
}]);

Because minifiers don't dare touch strings, the dependency declaration is not modified. The minified code would look something like this:

someModule.controller('ControllerName', ['$scope', '$http', function(a, b) {
b.get('/something').
success(function(c) {
a.someProperty = c.data;
};
}]);

The order of the dependency declarations matters of course because they will be passed to the function and bound to those variables.

Probably a longer answer than you were expecting but I hope it helps. :)
Thank you so much for this post, this gives me a little bit of hope and urge me to keep trucking.

I too was a man full of rejection:

1. I was kicked as a co-founder of a successful startup.
2. Upon finding a full-time job, a year later I was fired and have a lawyer to write demand letters for me which I never comply.
3. Found another job to work remotely that require me to have a Macbook Pro, but being financially short I converted my only desktop to a hackintosh. Then months later they send somebody at my house and upon discovery that I don't have a Macbook Pro I was fired.
4. Found another job, months later I was being shouted to leave the office and was fired.
5. Found another job, I was really happy I was into mobile app development, and 2 weeks away from release and shipping of the app, I was fired and the app didn't get shipped.

Right now I'm hoping to get into developing my own product, only if I have the strength to move on, and this post gives me a little bit of hope, I say 'Good luck, bad luck, who knows?'
DHS Ammo Story is Overblown
> Firefox used to have a button for subscribing to any RSS feeds it found in a webpage in the navigation bar. It was the only browser that did it

I'm pretty sure Safari did this as well - it was removed in Mountain Lion.
Yes, possibly enough to fight off the bad press even. Without such an initiative, I was afraid their hard work would fade into obscurity.
It's a training course that the people building the product need to go on (which, in this case, is a single person). Some kickstarters might send two of their people on a 3D animation course. Some might buy an expensive set of textbooks and other such training material. This one sends someone on a residential RPG course. Some kickstarters might need to buy some expensive hardware that she could not otherwise afford. That's exactly what this one is doing.

I could not disagree more that it counts as "fund my life". "Fund my life" would be paying for things that she was going to have to do anyway, such as paying the rent and bills (which she probably doesn't, being 8 or however old she is, but that kind of thing is "fund my life").