skysight-inc/HackerNews huggingface dataset:
In my country it is pretty regulated, you need to get certified and do 5 years after high-school to become an engineer. Or a basic "CS degree" would only require 3 years.
This is why if you get to call yourself engineer you pretty much stick with that. + It gets you paid a lot more.
SimpleColorPicker for iOS
Maybe, but "go away, I hate white people" seems a slight overreaction.
It doesn't seem surprising these kids are doing well--they're already top students, money's no worry, and they're hooked into the a successful social network. However, these ~100 examples don't characterize college dropouts. There are roughly 30 million total dropouts, and most of them are unemployed and poor:

http://www.theatlantic.com/business/archive/2013/03/the-myth...
Were the Mayans an especially just society?
I think so. You don't need a 3D artist -- models can also be created with a 3D scanner.

I also don't think (I haven't read the paper, yet!) you need to do anything to get the semantic sliders other than to label existing data. If you're going to design a single chair, it's probably more time efficient to have an artist make a 3D model to your specifications. On the other hand, if you're going to design something like a customized biomedical part with variations that depend upon the patient, then this could easily be a net win. Not to mention if you'd like to automate that design, you now have a much smaller dimensional parameter space to play with.
They could have an out of date view of the cluster. Like which databases exist, or which servers exist.

However, those cases are fine. If a database was created and a server doesn't have a copy of it. When a write comes in it'll be a cache miss so it'll hit the Raft system to get the info.

In the case of a new server joining the cluster, it won't get new data assigned until a shard group gets created and a shard gets assigned to it. When a write comes in if a node doesn't have a shard group for that time range, it'll all out to the Raft system to get the information.

So yes, it's possible for some servers to have a stale view of this cluster metadata, but we work around it by having them request the information on demand and periodically refresh the entire thing.
Oh boy I'd love to watch this guy in action in a twitch.tv stream, taking down a site (to clarify... white hat stuff!). It would be so damn fascinating to see how his mind works and how he makes the leap from 0 to exploit.
An article by Bill Gates about dropping out:

http://www.gatesnotes.com/Education/11-Million-College-Grads

"Although I dropped out of college and got lucky pursuing a career in software, getting a degree is a much surer path to success"
The 1.x versions of BSON are vulnerable, too, FWIW.
This is easy payment math. Assuming you start with nothing, your goal is $1M in the bank in 8 years, and you make average stock market returns (7%), you need to invest $7,800 per month ($93k/yr). That's approximately 1/3 of your $250k total pre-tax income.

The capital is there: the question is whether you can live the lifestyle you want in Silicon Valley on $90k/yr. (Assuming Uncle Sam takes ~35% in taxes and you incur no debt otherwise.)

In Excel:

=PMT(0.07/12,L18*12,0,-1000000)
> And yes, that does happen. A lot.

You don't seem to have a grasp of the real world here. What actually happens is that people will take credit or get credit from other's ideas regardless of gender. That's what happens a lot. It's only your own bias that you think it's noticeably women being the victims. Welcome to the world of equal opportunity.
How would he know if he's "bothering" them without asking? Not everyone in the world is reflexively atheist.
(Tedious disclaimer: my opinion, not my employer's. Not representing anybody else. I'm an SRE at Google, and use some of this stuff all the time.)

In all honesty, this diagram is missing so much information that you won't learn very much from it about how we do things (and all the things you can't see are confidential). It's more like a map of the relationships between the few bits that have been published.

However, I would tend to agree with your final suggestion that data structures are much more interesting than code.
See this Reddit post for the time spans on previous agreements:

http://www.reddit.com/r/worldnews/comments/387elg/wikileaks_...

As you can see, there is a huge range.
Really great read, I recently lost a friend who was among many other great things Jewish. As a "Gentile" I found the entire Shiva process both historically / anthropologically interesting and very helpful with the mourning process.

My thoughts go out to her and her family.
The James Webb Space Telescope – An Astronomer's Dream
The article misses an important aspect of microservices: They're reusable!

Almost all of the swathe of microservices we've developed internally are general-purpose. We've built a dozen or more user-facing apps on top of them. If I wanted to build a new app today, I would typically sit down and write a Node + React app with no backend code needed because I can just call our existing services.

For example, we have a microservice dedicated to storing documents. With this I can create a todo list, a blog app, a Reddit-type link aggregator with comments, etc. If I need login, there's a microservices that mediates between an identity data model and an OAuth account registry. If I need an upvote/downvote system, we have a microservices optimized just for that. We have services for sending notifications across different transports (email, SMS); "followings" and sending digests about updates to things you're following; organization trees; verifying email addresses and mobile phone numbers and other verification sources; processing photos, audio and video; collecting events for aggregating in an analytics store; etc.

This ability to "pick and mix" functionality you need is the real beauty of microservices, in my opinion. It's a huge time saver. We just whipped up a new site recently where 95% of the work was purely on the UI, since all the backend parts already existed; the remaining 5% was just code to get data I to the system from a third-party source.

This does require that you plan every microservices to be flexible and multitenant from day one. It's a challenge, but not a big one.
So, again, you dismiss the claims just because they're not the experts they say they are.
No, of course not. It's really easy to come up with a system that always comes up with "good" results if you rule out "screwy" voter preferences, with a sufficiently restrictive value of "screwy".
Timestamps should mostly be supplied by the client. They can be present or in the past, it doesn't matter.

If a write succeeds only partially, it will most likely be replicated up to the other servers (and thus be consistent) by the hinted handoff queue. This should be a fast recovery. Anti-entropy is for some much longer term failure that needs to be resolved.

Our use of hinted handoff and our goals for that are just borrowed ideas from Dynamo (the paper not the AWS DB), Cassandra, and Riak.

The issues around consistency are only for the failure cases. During normal operation you'd see a consistent view (within a second or some small delta).

Mostly the system is AP, with some parts that are CP. But if you really examine it, it's neither pure CP nor pure AP. It's some other thing.
This is the patent: https://www.google.co.nz/patents/US8950867

Abstract: A system may comprise a selectively transparent projection device for projecting an image toward an eye of a viewer from a projection device position in space relative to the eye of the viewer, the projection device being capable of assuming a substantially transparent state when no image is projected; an occlusion mask device coupled to the projection device and configured to selectively block light traveling toward the eye from one or more positions opposite of the projection device from the eye of the viewer in an occluding pattern correlated with the image projected by the projection device; and a zone plate diffraction patterning device interposed between the eye of the viewer and the projection device and configured to cause light from the projection device to pass through a diffraction pattern having a selectable geometry as it travels to the eye.
Which part in particular? Seems pretty accurate to me.
Thanks for asking, I should have made this clearer, both here and in the documentation.

This library is for building native Android apps (written in Java) that can talk to a Meteor server via their DDP protocol.

On the other hand, Meteor's built-in app system is for building wrappers around web applications that are built with HTML/CSS/JavaScript. For that, you don't need an Android client, of course, because it just uses their normal JavaScript libraries.
This is the third Raft implementation for us. The original was goraft, then we attempted to make our own streaming raft implementation for high throughput.

This time around we realized we should only put very low write throughput stuff through Raft. And we wanted to pick on that has been out for a while and running in production in many places.

So we chose the Hashicorp implementation because we know them and know that it's been in production for a while. Combined with the fact that it can be backed by BoltDB, which we like.
Forget J2EE, Java itself is dead. It got a bit of a shot-in-the-arm when Google chose it as a language for Android and it's had some activity around the JVM (e.g. Scala and also Twitter's fork of OpenJVM). But it's dead.
Worth noting that they provide helpful functions for pointer-ization:

https://github.com/aws/aws-sdk-go/blob/master/aws/types.go
Hard to find specific evidence on this question, but I believe most of the details of the ministerials are public, and its main goals are public (because we're technically mid-Doha round, but we know all the basic arguments and points).

However, when a new member considers accession, they have one on one negotiations with all existing members, sometimes in private.

The common talking point is a little misleading in that it suggests that this is unusual (it's not), or that TPP will become binding before it becomes public (it won't).

The common rebuttal is a little misleading when suggesting that every deal is negotiated this way. (Not every deal, but enough so it's probably not that big a deal.)
Paul Buchheit wrote a wonderful post, after similar circumstances, that I often re-read:

> On a more practical level, what matters most in our day-to-day lives is that we're good to ourselves and to each other. It's actually not possible to only do one or the other -- we must do both or neither, but that's a topic for another time. Sometimes, when I write about startups or other interests of mine, I worry that perhaps I'm communicating the wrong priorities. Investing money, creating new products, and all the other things we do are wonderful games and can be a lot of fun, but it's important to remember that it's all just a game. What's most important is that we are good too each other, and ourselves. If we "win", but have failed to do that, then we have lost. Winning is nothing.

http://paulbuchheit.blogspot.com/2012/03/eight-years-today.h...

May Sheryl and her family be free of suffering.
That's why later on we'll be adding per query request consistency levels. For now, we're focused on the AP use case where you don't need an absolute guarantee.
My first flash drive was 128MB-- worlds smallest can hide under a dime
A few remarks:

1. Arrow's theorem concerns the situation where your election procedure needs to deliver (not just a single winner, but) a ranking of all the candidates. You might hope that relaxing this condition will help, but ...

2. There's a closely related theorem with the magnificent name of Gibbard-Satterthwaite, which says that if you have more than two candidates, any procedure that takes in ranked preferences and spits out a single winner must (1) give all the power to one voter, or (2) leave at least one candidate unable to win whatever the voters' preferences, or (3) be susceptible to tactical voting, meaning that in some situations a voter does best to rank the candidates in an order that doesn't match his or her actual preferences.

3. However, there is a loophole "at the other end". For instance, if the input consists not of rankings but of scores (e.g., from 0 to 100), then the conditions of Arrow and Gibbard-Satterthwaite don't apply. And, in fact:

4. If there are only three candidates then "range voting" or "score voting" (each voter scores every candidate and the candidate with best average or total score wins) has the desirable properties Gibbard & Satterthwaite forbid for ranking-based voting systems. (Almost: sometimes optimal voting strategy might require you to give two candidates the same score even though you have a definite preference between them.) But, alas,

5. With more than three candidates no score-based system has those properties either.

(An interesting simplification of range voting is "approval voting", where the only possible scores are 0 and 1.)
Thanks for the reply. My main concern is that my employer might be contacted, and subsequently start taking actions to replace me. Is this something I should be concerned about?
in that case.. i thought about it and, if i can still change my order, i think i want the blueberry
Out of curiosity, what management tool do you use to orchestrate all these microservices?
Show HN: xps to pdf converter
How Criminals stole $50M in tax returns, and how this will happen again
I don't disagree with the first sentence, but you can't deny the fact that the NSA has stored private information on most, if not all, American citizens.

Regardless, it's starting to sound like you're encouraging a false dichotomy. Like I said, it's not unreasonable to believe that by restricting the power of the NSA you're creating a society that would be more accepting of LGBTQ individuals. I can guarantee you a freer society is a more accepting society. At the same time it's kind of silly to talk about prioritizing positive change when realistically as modern individuals we probably have enough time and intelligence to devote support to more than one cause, but when you asked the question I wanted to make it clear that you cannot have the positive rights of marriage and equality without the negative right of privacy.
Cultural fit is a thinly veiled excuse to not hire perfectly qualified people usually because of some (usually illegal) prejudice that can't be expressed another way. It's a way to skirt the law and a simple reason to turn down applicants that can't be questioned.

It also seems to refer to expected traits of not only applicants but current employees that cannot be mandated by contract explicitly. I have seen it argued that not working weekends went against the culture of a company and therefore there was a bad cultural fit. What a load of B.S. It seems these cultural values into which one must fit are always negative ones from the point of view of the employee. Free work. Limited, narrow thinking. Even pleasing and worshipping the boss. I have heard of very few companies that value vacation as their cultural values and would turn away people who overwork themselves into burnout.

Either way, it's something toxic that companies would be much better without.
My problem with the hype around this auto-tagging is that Microsoft had this in OneDrive months ago:

http://www.pcworld.com/article/2876548/microsoft-onedrive-ad...
Also interesting to note that > 50% of all developers use Windows. So much for the other comments saying devs only use Macs.
> while Chinese does the opposite

Can you elaborate on that? I'd never heard of such a thing.
I would not. I am American and despite the fact that what I think he did was right, the manner he did it was wrong.

Domestic Spying is NOT OK.

International Spying IS OK.

He released dozens of files regarding international spying. Setting US efforts back dozens of years, endangering lives of US assets.

Sorry to say but that is treason.

Treason has a price.
All of these stories suggest United States students who simply haven't done enough shopping among United States colleges, of which there are thousands. Most of the situations described could fit the same student getting a complete tuition waiver (variously deemed "financial aid" or a "merit scholarship") at plenty of United States universities. List price is not the price that many college and university students pay to gain their higher education degrees, and full list price is plenty low at many United States colleges and universities.

On the other hand, as an American who studied abroad (after gaining my undergraduate degree here), I have to say I'm happy that American students are considering studying overseas, as that has educational value (being in another country) even if the college is a poor value:cost trade-off. Especially studying in a non-English-speaking country (as I did) is very educational, and I highly recommend that to any American.
Because that's not how bitcoin even works??

Users transmit transactions to the network, where miners put them into blocks, generate hashes, and add them to the chain. Nodes always trust the longest chains as being correct. Miners control the blocks, not users.

This isn't some Starbucks or Target where a centralized policy maker is deciding what to do based on "user demand", assuming users were even able to collude.
You're right trays are quite common a lot of countries in restaurants or other places where the change is being carried to you.

But at least in my experience they are not very common for giving change in shops.
And I should believe you, rather than the women to whom this happens all the time, because... why?
How is this not anti-trust (and simply un-american)? This is as bad as Microsoft in the 90's subverting rival DR-DOS:

http://en.wikipedia.org/wiki/DR-DOS#Patching_to_counter_Micr...
No, I disagree with the substance of their argument for a bunch of reasons, but that's not what my comment was about. I'm not writing a formal rebuttal; I'm only pointing out that their credibility, which the EFF is directly appealing to, is hollow.
"Screwy" in this context means the sort of intransitive situations referred to in the parent of my last comment.
To answer your question, it was likely a counterfeit detecting pen[0] that only leaves a visible mark on counterfeit notes. I generally only see them used on $100 bills; rarely on anything smaller.

[0]: http://money.howstuffworks.com/question212.htm
It is actually a cost and Walker is wrong. What changes is how the cost is spread. If you buy a building and you spend 1M you will have -1M cash and +1M in property. But since the building will age you will have to amortize it, let's say over 10 year. So you will account 100K as an operating expense and you will reduce the value of that building on your capital, so at the end of the year the build value is only 900K. And you do the same for the remaining 9 year.
But this make sense, if I buy a building, I'm not going to use it for just one year.
If you buy a company it is a little bit different. Usually the physical assets goes on the balance sheet as explained above. The difference between the buying cost and the assets is called Goodwill and it is the only part that doesn't need to be amortized. Goodwill are many things, the brand value, the internal know how etc etc and doesn't need to be amortized. But you are required to re-evaluate it every year and if it has lost value you have to write it down, so it is a cost.

If you look at it carefully, the accounting rules make perfect sense. Otherwise buying a building (or server) for my company will impact the margin of just one year and it would be difficult. The problem is that Goodwill is difficult to evaluate, so managers could decide to re-evaluate it as they want in order to boost their bottom line. But it is bad management, not bad accounting.

Regarding is point on sales, it is not even accounting, but the dumb use of financial ratios. Usually the company could use the earnings call and the notes on the balance sheet to explain this shifts. But again, it is a call on the management side to explain it and sometimes they prefer not to explain to hide from competitors. They need to find the right balance between hiding their moves from competitor and informing the investors...
Show HN: SwiftStock: Yahoo Finance made simple in swift
I think I know what youre speaking of, my recollection growing up in the 90s was that the bill at a restaurant would always arrive on a tray, and then any change, mints, customer receipt, change would be returned on the same tray after payment was made.

Now with debit cards (interac, not mastercard) being the norm its standard to get the bill and then have them bring over a wireless debit machine (and has been that way for at least 10+ years)
> if you are only using the NT native API then it should work just fine

I believe I had trouble executing any instructions in the new process at all. If you can make it work I'd like to see your code, otherwise I'm skeptical.
Thanks for the more detailed explanation! Really looking forward to further posts -- not to mention 0.9!
We have these in Canada, I'm pretty sure I've used these in Pennsylvania and Michigan as well, not sure where these aren't used actually.
I work at Microsoft and the number of Indians there seems disproportionate to me. I too wonder why so many of them come to the US. Maybe IT education in India is really strong?

Two funny things I observe regularly:

1) Sometimes I take an MS shuttle to work. The shuttle is full, and I'm the only non-Indian in it.

2) Sometimes I'm in my building's lobby and when I look around, I'm the only (or one of 2-3 people) non-Indian there.

I pity those guys because they have to wait for 10+ years to get their Green Cards, even if they're EB-2.
I tested on our app (which uses BSON-ruby 1.9.2) and was surprised to find that the detection code indicated it was not vulnerable. Turned out it was because we also use bson_ext — bson_ext replaces the vulnerable method with a C implementation which doesn't use regexes.
In canada you can have five coins in your pocket and still have $10 for lunch, but what strikes me weird is visiting americans' homes and seeing crumpled $1 bills stuck in the couch!

Where I live the smallest bill is $5 and is worth picking up, but to the Americans I know it almost seems like all change and $1 bills are worthless. Very foreign!
"Broken" is a subjective thing, but quirks that break extremely well established patterns (like how people validate the beginning and end of a line in regex) is where a lot of security issues tend to crop up.

Considering that I would venture to say that this is indeed a broken thing since it's a convention that I've only heard about in Ruby. It's a special snowflake in a component that developers use almost exclusively for validation (regex), with a pretty huge gotcha, especially because it appears to function as intended.