skysight-inc/HackerNews huggingface dataset:
> You always need someone standing by in case of some terrible disaster that cannot be handled automatically.

If it's a really terrible disaster, a once-a-decade kind of thing where everything goes haywire and you need as many staff as possible to get online ASAP, then yes. But aren't we talking more about the kinds of "disasters" that happen once a month or so, and can be handled by a few staff (not waking up the whole team). To me that sounds more like just staffing for normal operations.

At large engineering companies this is typically handled via literally having someone standing by, i.e. formally on duty, rather than having off-duty employees be on pager duty. There'll be at least a bare-bones staff on the after-hours shift (probably not in all offices, but in some kind of 24/7 operations center), enough of a staff that reasonably foreseeable things can be handled. Of course there are some pros and cons to that from an employee perspective. On the one hand the night shift isn't that pleasant, but on the other hand your responsibilities are at least formally limited to 40 hours/wk; if you're on night shift one week, you don't come in during the day, or carry a pager during the day.
My thoughts were more like it was the first indie game because it was the first game I recall being referred to as "indie"

Before that they were just "games" or "a cool new game" or stuff like that. I dunno.
As a C++ fan in the C vs C++ discussions, I remember the days it was despised by game developers...
Why doesn't he like us?
What good does that do if the web servers team aren't on call? I thought the point was to have someone on call to deal with things.
Your perception is wrong. Every year they do a census. Of the people who filled out the survey most earn under 100k a year, with the average being around $40k. To be 5% of the US you need to be earning 188k a year.

http://feralgraphing.blogspot.com/2011/08/income-distributio...
http://www.nytimes.com/interactive/2012/01/15/business/one-p...
Ferris Restaurant, Edinburgh. I went there in 1990s and again a few years ago. Family run Scottish Italian restaurant. It was a bit strange seeing the same waiter after a 20 year gap (glamorous sharp suited younger man, plump slow ponderous but amusing older man, same as me except for the suit).

Closed. Overnight. A (no doubt fine) Lebanese opened instead.

http://en.wikipedia.org/wiki/Kitchen_Confidential_%28book%29
I can second this. If you can't fix the underlying reason that you were paged at 3AM it gets old fast
From the referenced study: "The measurements were conducted in a diffuse sound field at a reverberant noise chamber at the NIOSH acoustic testing laboratory. The diffuse sound field ensured that the location and size of the smartphones did not influence the results of the study. "

Having done sound testing extensively, you can be sure in an airplane positioning and sound source and sound type can drastically impact your measurements. Multiple reflections can re-enforce, or reduce the measured level. The type of sound measured is very important as well.

He's not measuring pink noise on the airplane, what the measured level of a particular sound is, needs to be normalized to really understand what effects it will have on you.

I'm sure in a good test setup the smartphone can get you pretty darned close. I'm more concerned with this guy's test setup than the equipment used.
All those remind me of Steam. Which was new at the time, yeah?
Object Oriented, Test Driven Design in C# and Java: A Practical Example Part #2
There should be more focus on what Chicago's uniquely good at

Do you mean whining about how we deserve to be a tech/manufacturing hub but we're not? Because we're pretty good at that.
Get ready to hear alot more stories like this in the next two years.
Definitely works in retail and not just for low-volume specialty markets. I shop at WinCo, which is a great supermarket and successful coop:

http://www.forbes.com/sites/maryjosephs/2014/11/05/millionai...

Also Bi-Mart, fantastic coop chain.
And it also doesn't encourage long compile times, so you might be tempted to do less thinking and more compiling.
You get the ability to use lightweight concurrency contexts (go-routines) + channels. Those are built in. The included library is very good.

But if you are used to generic programming and you think in terms of it, type handling in Go and might think it is a step backwards and Java might be close to what you'd want.

Even better, I think as C++, Rust is starting to look interesting. I am waiting for them stabilize it more (maybe get to beta 1.0 status), because I think it has some very cool things going for it.
It strongly depends on what's expected.

When we did it, the response times and time on the clock were clearly specified. Return the call/page within one hour between 8AM to 11PM. Later we scaled it back to 7PM and then finally to support only during normal working hours.

Whoever got the phone that week also got a small bonus for doing it to reflect the inconvenience of having to respond to calls on personal time. On average there was rarely a support call outside working hours so it really wasn't a big deal.
Why are you acknowledging Little Red Hen's rights to the original loaf of bread? Hen used communal property and facilities, why should Hen have any exclusive rights to the bread at all?!? What's different about Hen's assertion of control over the original loaf of bread (made from communal property) and a copy loaf of bread (made from communal property)?
At the same time it is sobering to learn that one of the more recent wildly successful indy games only made a few million at most.
From my experience, its usually mix of different languages. What ships in the final build might be C/C++ with Lua, custom script + some other custom text formats.

Just an example.

Then there is Unity, and plethora of frameworks where you write in some language and then it gets translated into another and there are just too many variations.

There are still games shipped done in Borland Pascal for that matter :)
"taxed 100%"

This is just not the case. Slavery is much worse, because it extends beyond money. For instance, as a slave, your children can be sold away from you. There is a big difference between high tax rates and being outright owned.
> Native code binaries can be beneficial in some cases.

Available in Aonix, IBM J9, Jamaica JVM, Excelsior JET

Just because OpenJDK doesn't offer it, doesn't mean others don't.
"It's not a great book by any stretch, but it did persuade me that successful localization needs to consider much more than just language."

Nice reference. The perspective is the important thing, the book is just the vehicle.
Proofs are programs but of a very different kind. For example, you don't care about performance.
Doom was pretty commercially successful...
None of the katakana are flipped, at least on my machine. I'm not sure which should be, I think they all are?
Wow, that's nice idea! Thank you!
> those issues will be overcome before deployment.

Really? We'll invent a 100% secure computer system? With no way to be hijacked? How about we build that system first, and use it to protect our social security numbers, credit cards, email, voting, and patient health information!

It's because there is no way to make a perfectly secure system. In a worse-case scenario, our enemy hijacks those 100,000 robots you wanted to send, all at once, and sends them against good guys.

> Set some parameters and tell the robots where they can and can not operate and under which circumstances and be done with it.

Some parameters... Like, holding a firearm? Mad at the United States' policies? Defending their home against invasion? Bowing to Mecca? Skin pigmentation?

Remember, war isn't even fought between nations any more. Most of our recent interesting enemies have been merely citizens inside of third world countries.

If your GOAL was "kill everyone inside of these borders," then maybe you could control that. That's never the goal, though. Not since Hiroshima and Nagasaki.

> Let the AI figure out who the bad actors are

Humans can't even do that.

> are and then help rebuild the country

That's a neat idea... How about we win hearts and minds with agriculture / health / construction / education robots FIRST, rather than sending an army of death robots to murder every human in a death zone?
There's a big difference having someone who is responsible for the operation of the infrastructure being on pager duty and the developers being on pager duty. In most development shops there would be no point in having one random developer being on pager duty. What if something breaks that he's never touched? Usually devops is first made aware of the issue, determines the cause, and, if it's a software issue, should then reach out to the developers who are responsible for that part of the code. A pager rotation among developers means there's something fundamentally wrong. If devops is constantly being paged because of shitty software, they should be the first to recommend that the QA -> release process be evaluated because it's clearly broken.
I agree with these points.

I'm a big fan of developers being on call for their application. It puts the pain where it belongs--with those building the systems (modulo lower-level errors--such as power failures or network outages--those should go to the appropriate place).

However, that pain should only rest with the development team if they also have the freedom and will to spend time dealing with it. They will have spend time (either a constant tax, or more likely, with occasional sprints) to reduce operational pain. They are in the best position to reason about the tradeoffs and pragmatically reason about priorities.

In my experience, this produces the highest code quality and the highest team morale. I also like the rule -- if you're paged during the night, sleep in the next day.
[topcoder] Algorithm Tutorials
Actually, he's been doing this for a while. When he was at XCF at Berkeley in the early 90s, I had contributed to his FMPL (Frobozz Magic Programming Language) project, writing MUDs in it. (I wrote a Dikumud/D&D like system).

He's a wiz, and his C code was humorously commented that makes it a joy to read.
"Indie" doesn't just mean independent. It is (or was) a specific scene, centered to an extent around TIGSource and its forums. The games that came from this scene are what put the genre in its current spotlight.
This sounds like an implementation as opposed to design flaw. Enigmail should be throwing up red flags all over the place when duplicates exist.

That being said, this is perilously close to the "No True Scotsman" fallacy.
Cool site! Max Krohn (https://keybase.io/max) and I are meeting with some people working on various PGP projects in Germany in April, and one of the things on our personal agenda is the ideal future of key distribution. We don't really want to be a sole place to look up these keybase-style social media proofs. We also don't think they belong inside the keys themselves.

One complication: looking up a key by email and trusting 3rd party verifications is philosophically pretty different from what Keybase is doing. So we have to figure out how to resolve this. For example, we don't even have an email based lookup at all (!), because we have no way of letting a client verify it's true. I don't know if we can be convinced to change this. We're looking forward to Yahoo's and GMail's work on their E2E projects because it may help verifying email addresses publicly.

And to be clear: we're not in the email business, so we want Keybase-style key proofs to be useful to mail clients like Whiteout. We'd like to work well with everyone.
What about Doom, Wolfenstein, Duke Nukem, etc? Or Elite?

All pretty indy and commercially successful.
Thanks! I'll try to answer:

Regarding what you say about removing the ads, it is true, but it seems to me that it is the same thing everywhere (at least for the apps I tried). Then right after you use Touch ID it will tell you the price, and you still have to confirm if you want to buy it or not (it's just 99 cents btw)
Just one more thing, after purchasing the app removal, the app has to closed and reopened. Sorry about that, but that's how it is

Regarding the points, if you are quicker you'll get the bonuses, and if you wait too long you'll break the combo. I felt like this was a good way to reward speed.

Let me know if you have any other comment!
I assume the income inequality here is owner vs worker, rather than above average worker vs below average worker. I expect the gap between workers in most fields is much smaller than the gap between the owner's profits and the salaries of each worker.

The idea is that, in a traditional company, the owner (or stockholders) puts up all the investment and risk and in return, get the lion's share of the payoff. In the coop, there is no 'owner' and any profits that aren't reinvested in the company are divvied up by the workers. The trade-off is the difficulty in finding investment capital to get started, which is why many coops are simple businesses like cleaning services that can be started by workers pooling their resources.

Also, in regard to below average workers, I suppose that in many fields a coop could use productivity/skill/experience/etc to scale how big a slice of the pie each worker gets. This would allow any reasonable worker to be hired, while encouraging competitive productivity. It would all depend on the coop's rules.
Scamming face to face is a slow, risky process. Email allows me to try to scam millions or even billions in a moment. For essentially no incremental cost. So even if I get a hundredth of a percent conversion on the scam, I win. It also allows me to scam for vastly lower stakes. I'm not going to risk a face to face scam for a penny, or even a dollar. But via email, there's no real floor on how high the stakes are before it becomes unattractive. Said another way, if I send 100 million scam emails, and I convert 1/10th of 1% for a dime, that's $10,000 for little effort, investment or risk (because, really, who's going to hunt you down over a dime).
TFA says the GnuPG code is pretty rough. Has anyone (with crypto knowledge) looked at it? Confirmations and denials welcome.
Pager duty is not a band-aid. It CAN be, for poorly-managed companies, but even the most conscientious and knowledgeable company in the world is going to have unexpected failures.
First, let me unequivocally state that I'm not a homophobe by any means. A large number of the founders and initial employees were gay men, with strong ties to NYC Media and Wall St. They were hyped as being the Queer Eye for the Straight Guys of eCommerce. The people who were going to save boring straight people from themselves. The entire thing was a ponzi scheme designed to create a lot of hype, and take money from fools. By the looks of it they succeeded.
Actually, this was around 2008 or so, so Steam was already out for a few years. Most of those games hit it big on XBLA before heading to Steam a few years later.
The first-responders at my company are considered higher up on the totem pole. They keep the ship afloat, while others get to sleep blissfully ignorant to the latency that's causing replication to shit itself...

If there is an issue that another team is responsible for, we open up tickets on that team to address the issue. We take our jobs seriously, and make sure things get taken care of. It's not an easy job, but it's everyone's responsibility.

You also need to have the bosses on board to ease the pain of on-call. They need to allow you to come in late, leave early, or take the day off. They also need to be mindful of on-call fatigue and shifting the pager around to mitigate that.

Maybe we should stop treating first-responders as the low people on the totem pole, and treat them as everyone else. They keep the wheels running at night, and you may not be getting a paycheck if there wasn't someone there at 4AM to answer the phone.
Yeah, but you have to be very, very good to get one of those internships. I'm a mid-top tier programmer (better than most of my cohort) from a modest state university. I've been applying everywhere, and there's no way in hell I'll make close to $20k. I'm pretty good at what I do, but there's a gulf between what you get if you're good and what you get if you really good.
They are on call. It's a big company with multiple teams, each team has someone on call.
First Ubuntu Touch phone ships for $190, unlocked
AOT compilers are available in many licensed JVMs, but one is planned for official Java around Java 10 time-frame.

http://cr.openjdk.java.net/~jrose/pres/201502-JVMChallenges....

Slide 12.
Because they felt their third-party sellers were too slow.
Nice writeup. I fully agree on that approach.

Some time ago I implemented "invisible" keys for http://privacyapp.io on iOS, with support for HKP and keybase.io API. It works quite well. The only problem is that keyservers from SKS pool have different versions of software and response can be randomly broken for the very same request.
Writing a F# Type Provider
Until I read the article I was having a hard time reconciling the headline (elementary school teachers) with your post, since I don't recall many elementary school math tests featuring questions where partial credit was possible, but the study actually covers grade 6 through high school, which makes way more sense.

Since I can't see the paper: did they type these up, or maybe have one person re-write all of the papers going to both graders? Maybe things are different in Israel (where the study was conducted) but handwriting would have given a stranger at least an 80% chance of correctly guessing the sex of the test-taker in the schools I attended.
Using -isystem rather than -I makes gcc/clang not emit warnings for headers found in those paths, which does extend to -Werror.
Awesome. That's exactly what we have on React Native :D
We want to make sure that when possible, we choose APIs compatible with the future of the web.
Top Five Reasons You're Wasting Money When You Don't Know How to Code
The world's most-trafficked mammal – and the scaliest
Depending on the size of your team, that somebody should be in ops. That said, if you're a smaller team of only developers, you're right, someone should always be on-call.
I agree in the sense that we shouldn't let unvaccinated kids go to school and risk the health of other kids.

But I also think it's important not to poison the long-term approach in the process. I know a lot of anti-science people and for many of them it stems from a few really bad experiences where somebody just beat them over the head with science. Then they latch on to any crackpot who claims they're about to revolutionize science and do away with "scientism."
> Million dollar sound systems, pyrotechnics, and the kinds of people who can make that happen aren't going to show up at a Rainbow Family Gathering anytime soon.

Yeah, i'm not sure that would even be appreciated. Full disclosure: i was at the Iberian Peninsula Family Gathering in '11, and i haven't been to Burning Man (am kind of motivated to, though, in a sort of long-term TODO way), so that's my experience, but my impression is that the mentalities are rather different... I feel the Rainbowers kind of like their toned-down way of doing things (e.g. explicitly no stereo systems)...
> In Servo, how do you do interaction with the DOM like `clientHeight`? It just pauses the entire JS engine while it goes and talks to the UI thread?

Yes, but we'd like to experiment with new APIs in the future like `getBoundingClientRectAsync()` that will allow pages to do that kind of thing asynchronously.
I suspect they'll eventually be cheap and reliable enough that most homes have one, just like smoke detectors.
Thanks for the link, cool series!
Uhh... http://github.com/explore ?
> In math, the girls outscored the boys in the exam graded anonymously, but the boys outscored the girls when graded by teachers who knew their names.

I get that there's such a thing as "partial credit," but seriously? What kind of math are they teaching?
The real goal here is not to provide state-level security; it is to increase the cost of massive surveillance by deploying the easy parts of PGP everywhere. The people who are highly dependent on security will run through the whole procedure anyway, they won't just rely on whiteout. "Johnny", on the other end of the spectrum, will see the privacy of his communication greatly improved againts passive attacks.

Much like HTTPS Everywhere, it is not enough to guarantee that your messages will be secure against a sufficiently-funded and determined attacker. It puts some power back to the people to enjoy better privacy of communication.
Pager duty is a natural consequence of devops done right; fix your shit or feel the pain. So, it's a necessary evil in systems development, IMHO. But I was on pager duty for the 10 most recent years of my career, so may have a case Stockholm syndrome.

Everything stated below about disruptions to your personal life are true. When you're on-call, you should just forget about personal commitments. When personal commitments unavoidably collide with on-call, you're at the mercy of kind teammates swapping with you.

A good team will cover you the next day if you had a bad night, but I think during every bad night, a little part of you has to say "f### this job" and given enough bad nights, well... I'm a single dad w/ a kiddo, and I can tell you there is nothing worse in life than reading a kid his bedtime story, having the pager go off in the middle of it, and having to say "sorry, son," as he begins to cry and say "not again, Daddy!" (True, and awful story.) Like I said, "f### this job."

Anyway, a funny point about devops/fix-your-shit is that there's an effect here which parallels the Peter principle (getting promoted to your level of incompetence) in some ways:

If you fix everything that causes you to get paged, then eventually the only things that page you are things you can't fix (the network, power event, etc). And while those kinds of wake-ups at least lack the adrenaline/stress component (just sit there and wait for recovery), they further reinforce the "f### this job" thoughts - because now you're literally being woken up for no reason other than to "observe and report."
Your comment seems to presuppose that income inequality is largely the result of differences in skill and/or work levels, which is a common viewpoint that is not necessarily correct. The alternate viewpoint is that there are a lot of hard-working people with highly valuable skills who are underpaid due to the way corporations are usually structured. In a typical corporate structure, the people closest to the money are the best paid, which doesn't necessarily imply that they are the hardest working or mostly highly skilled.
Microsoft employee here.

Microsoft somewhat recently implemented "Unified Engineering" company-wide, combining developers and testers.

I can assure you that testing is still done extensively.
The answer is to increase security by having widely adopted imperfect security rather than supposedly perfect but also imperfect[0] security with marginal adoption.

Having a secure initial message exchange is difficult and will always be difficult. Traditional GPG UIs are so obsessed with trying to solve that problem that they ignore the 99% case, in which something like trust-on-first-use is perfectly fine. The fact is, on average, users will be much safer with a TOFU scheme without any key servers or web of trust at all, as long as that scheme is sufficiently unobtrusive so that it actually manages to get adopted.

The sad truth is that I actually use a mail client with GPG support, but I basically never exchange encrypted email for two reasons: It's not automatic, and the vast majority of users don't have GPG support installed anyway - and I'm not going to push others towards using encrypted email as long as it's harder than "install this plugin and you're done". I have other causes to spend mental energy on.

[0] See other threads about problems with fake keys in the web of trust.