skysight-inc/HackerNews huggingface dataset:
I wonder also if they're at risk of getting their money stolen by police. Would a carload of mercs be able to stand up to a single cop on the highway claiming the money by asset forfeiture?
Why? It's purposely bad and it's spot on for this situation.
That depends on how one defines "watch logs". Looking at the text, no; looking at the metrics, yes.

We had a dashboard that would graph the number of errors grouped by the component over a given span of time. If we saw the chart grow beyond our tolerance, that's when we would break out elasticsearch-head or grep or $tool and try to dig into the details.

Do you have a tool in mind that does what you are describing and thus would supplement Kibana?
Have an escalation plan in place. If you're caught short while on-call, it's good to have a 2nd or 3rd who can take over in emergencies. It also helps to have someone you can get to cover you for short periods so on-call doesn't have to stop you doing stuff, e.g, having a colleague take over for an hour while you go for a swim.
I'm pretty sure the article was questioning the global optimality not the local optimality of the practice; it came across more as "hey, look at this stupid system" than "hey, look at this stupid guy."

Which isn't to say that the article has done convincing global analysis, just that I find handwaving about the "local optima serve as good proxies" assumption to be even less convincing that my gut feelings about the issue.
Arguably "years later" isn't instant.
Go is less verbose than Java arguably. Multi-threadedness in Go is very straightforward. Native code binaries can be beneficial in some cases.
Netflix Is Developing a Live-Action ‘Legend of Zelda’ Series
Two things we're particularly proud of at Keybase are (1) that there's no server trust of these proofs, and (2) we pin the entire state of the directory to the bitcoin blockchain, to prevent forking. [1]

In other words, if you ask for Twitter user X's public key, your client can check that proof on twitter itself (rather than trusting that a key server did it for you, like it would with email proofs), and it can trust a hacked/coerced server isn't hiding something specifically from you, such as a revocation. The latter is particularly hard to protect against. It also gets timestamping: you know the world has been seeing the same public key for Twitter user X for many months or years.

[1] https://keybase.io/docs/server_security/merkle_root_in_bitco...

[update] I gave mey a bunch more invitations, but I can be hit up on twitter (https://keybase.io/chris) for HN users wishing to jump our invitation queue, which is large.
Is it extremely hard to be a really good programmer?
I have a feeling that Jini will be re-invented in the future. There are too many good ideas in there to ignore.

"The End of Protocols" paper is another great read.
Owning means of production is so "few revolutions ago". Extreme income inequality is due to capital ownership.
I would amend that. Start with whichever you're fastest (not necessarily most competent) in. Once you discover whether the whole thing is worth the effort, move towards safe languages. That's basically Rust, Scala, or (functional-language-of-your-choice-or-) Haskell.

EDIT: Personally, I would start in something like Haskell or Scala just to do a proof-of-concept without having to worry too much about undefined behavior (C/C++) or absurd verbosity (Java), but then I am pretty familiar with those two languages. Maybe it would be worth learning one or two very terse languages to start with, just in case you hit upon a great idea? (Btw, I think Python or Perl qualifies.)

EDIT#2: As a sort of second or third order bit of advice, I'd encourage anyone to brush up on programming languages that might make you faster. It's a sort of "propellant" and can increase your speed exponentially.
- Do you have a how to post on how to move you wp blog to github, I've been thinking of moving my personal blog on github.

- Good job reading 5 book in a month your almost halfway of your goal.
I'm trying to read 26 book this year (fic & non-fic) I'm at 3 and halfway in 2 books.
In order to verify the signature, you'd have to get their public key. Since that's where this all started, we're just in a loop of untrustworthy ways to get someone's public key.
Ever tried to make a torrent containing millions of files? ;-)
I encode a public key and bitcoin address into my gravatar image.
That would be amazing if Java didn't have AOT compilers. (See my other comment.)
Ikea, for example, is private. Dell went private not too long ago, too.
All of this is doable. And none of this will happen. At least, none of this will happen until consumers and buyers start caring more about security than about the newest and shiniest feature.
This is very true. However, I recall it being in the first crop of commercially successful indie games: World of Goo, Super Meat Boy, Castle Crashers, Braid.
This is the first thing I thought of as well as I've been using keybase myself for a little while now and am very happy.
Judge Quits Forensic Science Committee--Calls Out DOJ 'Trial by Ambush' Tactics
Not my experience in scala. I've had a lot of places where in the Scala plugin for intellij, it incorrectly highlights errors, or doesn't discover the error until a full build.
Its amazing how fast SaaS companies or at-least good ones are growing..
This is absurd. Are you serious? The way you express your opinions is enormously important. It could easily be the difference between getting a raise and getting fired. Expressing your opinions in a way makes sense to other people and they take well to is the farthest thing from silly ever, it's like a #1 essential skill for life. On top of that, phrasing informs the message, and in this case I was not just complaining about the phrasing, I was also complaining about the outrageous statement being made.

For example, saying "React is the best way to build all apps no matter what" vs. saying "Compared to building native UIs with objective C, react-native made for a much smoother experience for me because of X Y and Z" are not only phrased differently, they are communicating different things. The first one is an absurd overarching dogma declaring every other app-building technology to be inferior to react with no backing whatsoever, and the second one is a useful and specific analysis of react in one situation compared to an alternative.

I can't figure out if you're trolling or not, honestly.
I scanned the article and couldn't find the reason they pivoted away from flash sales model.
Average CEO compensation came in at $15.2 million in 2013 for Fortune 500 companies.
There's nothing wrong with the Turing test as long as it is adversarial. The people who chatted with Eugene did not particularly try to trip it.

The beauty of an adversarial Turing test is that it is AI complete because almost problem you might want to throw at an AI can be brought up in a conversation.
It seems, especially for major corporations, that on-call/pager duty is quickly becoming the norm for software development teams. I do agree that pager duty is a symptom of a fundamental flaw within the system/architecture. I think it would be in a company's best interest to devote time in improving the reliability and stability of their infrastructure, instead of relying on the band-aid approach that pager duty seems to be.

Regarding #8 though, when you are pressured to resolve a complex issue within a short time window, it can absolutely induce a sense of panic for those who do not handle stress well. In my opinion, I believe the remedy for this would be to have two individuals designated as on-call at a time, assuming the team is large enough.
> I don't want your shit OOP and classes, take them back.

Most programmers disagree. Get over the fact that you are in the minority and JS has succeeded DESPITE the massive barrier to entry (beyond the simplest of tasks) and the monumentally messy spaghetti code that javascript (as a prototypical language) inevitably becomes, in larger projects.
http://www.aflcio.org/Corporate-Watch/Paywatch-Archive/CEO-P... says "The CEOs of S&P 500 Index company made, on average, 354 times the average wages of rank-and-file U.S. workers in 2012." That's within an order of 2 of the 600:1.

http://www.fastcodesign.com/3036217/infographic-of-the-day/t... gives it as "In the United States, the average American CEO makes a whopping 354 times the salary of the average worker." (One of the comments says it used to be 600:1.) Note that the "S&P 500" got dropped from the description.
I currently do pager duty (DRI) for a team within Microsoft. Like most teams that have this duty, we cycle a developer each week to have the responsibility to answer any escalations that might occur. The role of this developer is simply to mitigate the issue. Investigations into the root cause and potential preventative items are reserved for work hours.

The amount of escalations obviously varies from week to week. Some weeks I forget that I'm even on call (well that's actually not true as we have to carry a Lumia 1520 - the thing is a fucking brick) while other weeks are absolutely painful (waking up every couple hours in the middle of the night). Thankfully we have enough developers on the team that I'm only on duty every 6 to 7 weeks. What also helps is that my manager has no problem with me sleeping in and showing up late after a long night of escalations. Overall it isn't too bad and in fact sometimes can be fun to solve head scratching issues. Honestly, the worst part of being on call is not being able to make plans that would involve you being far away from a computer. You can turn this into a somewhat positive thing though by being productive at home whether it is cleaning, working on side projects etc.
The Turf Signaling Between Investors and Founders
I also think that you should try to keep the old URL unchanged.

I'm not an expert in this subject. Is it possible to use something like a Apache redirect or rewrite to implement the different domains under the hood, but show the users only one domain?
Penn and Teller: Technology has morphed the magic act
yes! wtf!! id, commander keen, duke nukem, shareware etc. etc.
Battle a Pokemon Trainer on Slack
Nice. Two things

1. When I tapped to remove ads it asked for Touch ID before I know what the price is. I just cancelled. I couldn't find a price anywhere

2. I feel like I should get more points the fewer times I let the ball go around.

Nice game.
Very interesting article http://research.swtch.com/gorace, but it's very old, published in 2010. First Golang stable release r56 in 2011/03/16 https://golang.org/doc/devel/release.html.
> The oral briefing required by paragraph (a) of this section shall be given by the pilot in command or a member of the crew, but need not be given when the pilot in command determines that the passengers are familiar with the contents of the briefing.

Maybe the airlines could make you take a quiz on the ground to get early boarding, and if everyone passes, no briefing!
At that price it only makes sense if you have something to automatically and agressively resize your app. Something like scale up to 6 dynos for a couple hours after you hit the front page on reddit, then scale back down.
This is a classic example of something I feel I should be able to follow and understand, but in fact cannot interpret as anything other than technobabble. I'm going to point to this as an example of how there are different levels of familiarity and expertise.

And to be sure: this seems to be a fantastic comment. I'm going to spend some time slowly working through it until I grok the terms.
There's a good chance it will be his next full time project, after The Witness is done.
Citing Tax Fraud Spike, TurboTax Suspends State E-Filings
Doing flash sales is good for profit (low inventory, good for sales b/c it's going away etc.) - but limited their overall topline revenue.
To echo akg, I've also been in experiences where the boss and team make the experience great. It's great if you like working on small tasks that are truly dynamic.

Sometimes, getting paged allows me to get my head clear of your normal responsibilities. I kind of use the pages as a nice refresher for my regular work. However, personal preference.

To comment on one of akg's points, the length of the schedule rotation can actually be a problem. Longer than 6-8, and you are then very detatched from the operational issues your team is having. Make sure you link up with the previous primary to get the run down on anything (and maybe even the person who was primary before her).

You definitely want to get more familiar with the team you will be rotating with, but:

1: Do not fear escalating to secondary / asking for help when you need it. While getting paged sucks, every team I've been on this has been one of the biggest guidelines. We would rather someone ask for help sooner, than do something they are unsure of / delay fixing something.

2 (More like an extension of akg's #6): This is something to clear with your boss, but when I'm on call I also try to put the engineering effort in to fix alarms that are less than ideal. If I get paged at 3AM for some bullshit reason, I will spend the time the next day to make it alert when there is something actionable to be done.

If you are at a startup it's probably unlikely you'll be reimbursed for your cell phone (receiving calls). However, they should have provisions for mobile internet. Using your personal cell phone for work-related activities could have interesting legal implications. If the company is getting investigated, your personal phone could (in theory) be included as work-related things have gone through it.

I've been on pager duty for a few years now. I've no regrets. However, I'm sure there's one day in my life where I'll be over it.

Best advice I can give while on call: keep calm and have fun.
Usually, there are practically no downsides to it, unless there is a fundamental problem in your $ORG.

1. First of all, it will get you connected to the users which depend on your $APP/$SYS. Hard. You will get to know their struggle/woes - it's not just some ticket you can work on at your leisure.

2. If it's your stuff that causes problems, you will get your shit together and make sure that it works, code defensively, and test thoroughly - whatever necessary. After all, you don't want to deprive yourself unnecessarily of sleep – or others, after the experience.

3. If it's not your stuff that causes problems, you'll get the oppurtunity to “yell” at the people responsible for it. And they must act on it - nobody cares on the why or what, if people have to get up in the middle of the night, it costs the company¹, and everybody gets upset.

It only impacts your health if you get called up regularly, and no actions are taken to remove the root causes of it. Or you can't take any.

It's less of a technical problem, but more an organizational one, so – as it already has been said in here – you should talk to the people of the team, not HN.

¹) If it doesn't cost them, be wary.
Hello, I downloaded the same malware on accident when trying to download utorrent. I have followed the steps below sucessfully, but I noticed that the installerT process keeps coming back after I reboot my computer. Also advice on how to remove it completely? Thanks, this thread has been extremely helpful.
Well stated. There are plenty of excesses to point to that have nothing to do with the small number of attendees making over $1M/yr.

Burning Man is a giant art party in the desert. It's becoming increasingly expensive in part because it's been increasingly popular, and so requires increasing facilitation (i.e. a temporary medical center complete with a radiology setup). Everybody that attends influences it, even the very wealthy, and the more interesting among these direct their influence intentionally by funding art and performance which anybody can experience.
The erratic (and at times outright maniacal) behavior of their CEO had something to do with their downfall also, from what I've read.
While I can still reply and in retrospect: I sort-of agree. The astroturfing comment was out-of-line. I'm not sure "bullshit" can be construed as a personal attack, but... reprimand accepted nonetheless.
It's that sweet sweet recurring + expansion revenue.

Edit: I should add -- this is what makes SaaS companies such a lucrative yet risky investment. It takes a lot of inside knowledge, and reading tea-leaves if a SaaS co will take off or not.
In Russian roulette, the chance of injury if you play is 1/6 and 0/6 if you don't. With vaccination the risk of injury is several orders of magnitude lower if you get it v. if you don't.

And the risk from not getting it effects not just yourself.

So, yeah, were the odds in Russian Roulette were such that playing it dramartically increased your health and safety and the health and safety of those around you, yes, the government should require it. But since those aren't the odds of Russian Roulette, it seems like a pretty dishonest analogy to use.
A Billion Degrees of Separation: Absolute Zero to Absolute Hot
This is how the Brits do it http://i.telegraph.co.uk/multimedia/archive/01394/20030330-R...
This phone is some Mediatek garbage SoC with a horrible OpenGL blob. It is probably reapportioned Android hardware.

It is certainly not the kind of tech one wants or needs to drive a converged device.

Hopefully Canonical gets less stupid in the coming months and finds a higher end hardware partner to ship that converged experience, because early adopters have been able to do it on their Nexus phones running Ubuntu Touch for over a year.
Downsides are that you become a slave to the pager. Everything you do for that week revolves around having to potentially take a page anytime.
Good timing, I just left a company after being on their security incident response oncall rotation for 2 years, partly due to the oncall. akg_67 has some great points (https://news.ycombinator.com/item?id=9011293), but I'll add a few of my own:

1) When you're oncall, your time and priorities are no longer your own.

At your kid's soccer game? A date night? Planning on doing any of those things? Be prepared to get pulled out at any moment to deal with something that could take hours to resolve. This was the part that really got to me. As much as I'd like to do any one of those example things, I had made a prior commitment to be available and had to honor that.

2) Know the response time and physical location requirements for responding to a page

Is this something you can just fire up your laptop and an aircard and jam on, or do you have to be able to drive to the office within an hour. Don't forget about driving through places with less than great cell phone coverage.

3) It can be fun

There was a part of me that really liked the adrenaline rush of getting paged in on a legitimate security issue and having to run the call and pull the right people in to get the situation handled. It's a great test of how well you know the environment and where all the pertinent information lives.

4) Know the team size and oncall frequency
akg_67's estimate was spot on. Anything shorter than a month is crazy and you never quite feel like you normalize. Since it's based on team size, know what the optimal size of the team is and that there's funding for it? My team imploded and at the end there were only a few of us on the oncall rotation. Bear in mind that oncall duty doesn't go away because you no longer have the staff to make it manageable.

5) Vacations and sick time are now more complicated

Who has to be oncall during Christmas/4th of July/etc? What used to be some loose coordination with your manager is now a give/take discussion with your team about who covered the last holiday and who's turn it is. It's all completely fair and reasonable and if you have a good team dynamic you can make it work, but it's definitely more complicated than telling Aunt Edna that of course you'll be home for Christmas.

6) Get paid for it

Whether in flexing the hours for the time spend working a page off hours or by getting paid directly for off hours work. No reason to kill yourself for no additional compensation (and there will be those hellish pages or that automated alarm that goes off hourly starting at 3am).

7) Put the operational burden for supporting a thing in the hands of the people who have the ability to fix it

There should be a cycle of:
Get paged
Root cause
Fix
Post mortem
Deploy fix so that thing never happens again

If you don't have ownership over the thing that's paging you, you're at risk of getting paged all night every night for something you have to go convince other people to take time out of their schedules to fix to solve a problem that they don't feel. Not a great situation.
Go Green!

No but really, this is like, every engineer's dream that his creation would someday save him
Because tech workers are well-compensated, and can pretty easily move themselves around on a risk/reward tradeoff, and also pretty finely tune an effort/payout tradeoff. And because co-ops are probably at least an order of magnitude less likely to produce a $10million+ payout after 5-10 years than a startup is.
> It seems, especially for major corporations, that on-call/pager duty is quickly becoming the norm for software development teams. I do agree that pager duty is a symptom of a fundamental flaw within the system/architecture. I think it would be in a company's best interest to devote time in improving the reliability and stability of their infrastructure, instead of relying on the band-aid approach that pager duty seems to be.

I can't see there ever being a time where there is no on-call requirement. You always need someone standing by in case of some terrible disaster that cannot be handled automatically. Better to have this a formal responsibility that never gets used, then to not have it and end up with an extended downtime because you can't contact anyone.

That being said, if you're getting paged continuously during on-call, then there's a bigger problem that needs to be resolved.
There are tradeoffs. And the tradeoffs shift over time. Sarbanes-Oxley has (on the margin) made it more costly to be a public company, so we're seeing companies hold out over time. (One can are argue that this strengthened the system - I will leave that argument for elsewhere)

There are some absolutes that force a company's hand.

1 - If they have VC money and the investors want an exit, they have to sell it to someone. It's very rare that the current owners will have the money to do this. (If they needed $10mm to grow, will they have $100mm liquid to help someone exit?) If they sell to a PE firm, the problem just gets pushed down the road 5 years.

2 - There are limits to the # of shareholders a private company can have. If you believe in employee ownership, this becomes an issue as private companies grow.
It's not just "overhead". The reality with BTC is that if you accept BTC, you're responsible for the basis of the sender, which is impossible to know.

Converting to fiat currency eliminates that risk.
Linus Torvalds and Git [video]
I'm on call for 2 weeks every couple months, one week as secondary and then the next one as primary. It basically involves carrying my laptop (and a wifi dongle) with me everywhere I go. Some times a server needs to be power cycled, but theres never anything crazy. It also completely depends on how stable your infrastructure is and how much fire-fighting everyone is doing. I thought it was a good learning experience.
Did chip espionage, IP theft give Samsung its 14nm manufacturing lead?