skysight-inc/HackerNews huggingface dataset:
>Such adjustments should be applied to expenses, not income, and neglects the fact that many expenses don't multiplicatively scale with location.

Only the big ones, housing, food, transportation.

>It's very possible to live a good life even in SV/NYC on $60k/yr in expenses, leaving tons of room for aggressive savings.

Bullshit.

http://www.city-data.com/forum/san-francisco-oakland/189180-...

>At the very least, tell me what bogus adjustment number you're using.

Pick any calculator. Here's one of many linked by the US Department of State.

http://www.bankrate.com/calculators/savings/moving-cost-of-l...

https://www.state.gov/m/fsi/tc/79700.htm

>It's a tactic but not a very good one. I've conducted my own split tests and anchoring with a high number tends to lead to much better results while not wasting your time on people who think paying a senior developer $120k is reasonable.

If it was between you and some other guy just like you and I asked each of you what you expected the salary to be without throwing out a number and you were $10K higher, I sure ain't hiring you. That's how it works.
It doesn't even have to be for the startup life. They could just leave to work at another established company. Though the rest of your point about being risk averse and so sticking with a job (and therefore being less of a flight risk) is more interesting and would be worth exploring.
The biggest one I've seen is "we pay them Y because they already made X."

So if it's biased externally it's gonna look that way internally if you're not proactive.
> This might be true and I hope they win.

Can you elaborate on this? Namely, the burden of proof is higher than 'might be true.'

I'm guessing you meant something more like, 'If this is true, I hope they win.' I can never tell, anymore.
Proper modern approach adds thermal, or at least 1 other biometric sensor. Just as Windows hello relies on more than a pic, plus IR, + thermal. I suspect Apple X does this minimum.

More features can, but not always, improve the model. As pointed out by Tim Cook it goes from 1 in 50000 odds of duplicate result to 1 in 1,000,000. And that's 1,000,000 that would need to try on your phone.

FBI is probably running load tests now to see if they can brute force.
Why would it ignore the "eyes open" requirement just because you're in the dark?
What are you comparing it to? Compared to Bash, I love the fact that everything gets returned as an object that you can query, rather than as a blob of text that you have to hack on.
Dreams of Confederate gold in Danville
Unfortunately for Google, paying women less because "They can get away with it" (ie, women are less of a flight risk), is still illegal.
Well, they sort of do, because those terms don't map so cleanly when you begin spreading into a multi-tiered architecture.

You could easily end up with 'server side' work, which exists solely to augment or support a UI, and is not part of the 'core' business applications/services.
What percentage of HIGH PAY ENGINEERING jobs in google have comp sci degrees, that's the true comparison. And then there is bigger issue here. It's really the obsession about percentages of women in X position. Here's another percentage what percentage of women and men didn't waste a thought on how they looked in their teenage years because they where so obsessed on how computers worked? I believe it is both very small and men are over represented there, and they are over represented in high paying computer jobs.
> so why not use C#

Because you need to compile your C# source first. With PowerShell you just write and run. Also in a PowerShell shell you can fart about and test stuff without actually having to write a fully working script in a file, i.e. it's got its own REPL.
That's an offtopic nonresponsive reply.
The Products Announced at This Week’s iPhone X Introductory Event
Yes. However, the seller wants to factory reset it anyway to avoid leaking data, and the buyer wants to factory reset it anyway to ensure the device isn't e.g. saving iCloud backups to the previous owner's account, or doesn't have some weird malware installed (iOS is pretty good at isolating apps, but not perfect, and also jailbreaks exist). So it makes it more important to wipe the device, because attacks are easier, but it's not introducing a fundamentally new requirement.
Haha that'd be ridiculous! Imagine working all night and getting paid the same as someone who works half as much.

That being said, salaries are not determined by how hard you work but rather how much the company needs you to stay.
But that's irrelevant here. FB is likely getting sued by patent holding companies who aren't reliant on or using React. So the patent clause doesn't really get FB anything against patent trolls.

It does get them leverage against legitimate patent holders. There have been reports of companies having to pay in some roundabout unspecified way royalties to FB for React as part of a large patent licensing deal.

I'm somewhat skeptical of these reports, but if there is direct revenue to FB from this clause it would be the Occam's Razor explanation for their intransigence.
4 steps for hardening your Cloud Storage buckets: taking charge of your security
> One of the women suing complained that a man was hired a level above her with the same years of experience. They both had four years experience.

It's impossible to say without more information but it could just be a case of the old 4 * 1 year experience for her and 1 * 4 years experience for him. Comparing people on years of experience is the sort of irrelevant laziness I'd expect from a recruiter, not a developer.
And you know who terrorists recruit? Children.

You do care about the children, don't you?
Funny thing is, my old OS project [1] is more or less that - it could be a typical OS with separate tasks and so on, but it is effectively a single program, and can easily be compiled as a single program with all the standard calls replaced with OS-level implementations.

In practice, these are two different sets of use cases - in one you want clean abstractions, process separation, storing message passing and so on, in the other you want to get the call from your code into the libservice ASAP. Trying to (unwittingly) combine the two gave me quite a bit of grief.

Another disadvantage is a lack of any protection (at least in my implementation), since everything shares the address space.

Anyway, it's odd to see that a random idea i had 17 years ago is actually starting to get used.

[1] http://orbides.org/aprom.php
I even have problems with Intel card from time to time.
Sure, lack of advancement indicates a lack of ability. It's an old rationalization, but it's a post hoc fallacy.

That is: lack of ability to do what? Can you clarify?
This seems like a trade-off we're already okay with making.

$ du -h /boot/vmlinuz-4.4.0-93-generic
6.8M /boot/vmlinuz-4.4.0-93-generic
$ du -h /usr/bin/docker
12M /usr/bin/docker
It's honestly not even close. Have you read about the events in detail? I too was under that impression until looking more into it. Are you aware of the unknown sniper agitators?
I agree with everything you said, and your experiences match my own. I still say that situation leads to formulaic, systematic management.

Let's say that GOOG developed a sophisticated machine learning algorithm that made all hiring, firing, promotion, and compensation decisions. The code is open source, and everyone can see that it doesn't contain explicit logic for bias.

Now, a short, 44 year old, male engineer sues because of a statistically significant observed bias against one of his cohorts. Is the program biased, or just insightful?

With humans, it seems we have no choice but to assume their collective algo is biased. And it often is! But, when you're a massive monopoly with tons of cash, the safest thing is to make formulaic decisions that are statistically clean. It's just good business.
Premium SMS malware #EXPENSIVEWALL infected millions of #Android handsets
Really? I'm guessing you haven't spoken to many people who are proficient in it. I'm certainly not, but I can still appreciate the fact that you are working with Objects instead of text blobs, you have access to a decent IDE and a great help doc system.
Why? Blue Bottle customers are hipsters who like to pay extra for faux fancy goods. Why would they be especially likely to disacommodate themselves to benefit faraway people?
Who would want to work at such a place? Last I checked this is still a free country and you can work wherever you want.
With CSScript you don't have to compile first. It runs as a script.
Ethereum Announces Metropolis Hard Fork Coming Late September
Awesome article. Thanks for sharing.
This was us! Added CloudFlare in front of every bucket with our own "cdn.example.com" DNS name and changed every reference to s3 in code. Didn't even know S3 had problems today until I saw this on HN. (note: This outage taught us to set up monitoring of the S3 assets separate from the "cdn")
FRUSTRATED TRUMP THREATENS COUNTRIES TRADING WITH NORTH KOREA
1. Then you have the option not to use it, and always will (biometrics are used to augment passwords, not replace them).

2. Using passwords as a security measure increases the likelihood that a malicious actor will beat them out of you with a five-dollar wrench (and this does not mean that passwords are a bad idea).
Thanks for making these points explicit.

Years experience is not an indicator of seniority. I have two friends that graduated at different years.

One has more than 10 years experience. The other has three years.

10 year guy has been working with jquery and HTML the whole time. He avoids any other problems or domains.

Three year guy wants to work in every area possible. He actively pursues internships and work that provides a wide range of experiences and technical variety.

Now who do you think is more valuable as an employee?
You give companies too much credit. When it comes to layoff time, most companies don't know or don't care what your individual value is. They need to make a number and will cut whatever they think they can to make that number. Most of the time, if they actually try to "rightsize," which isn't that often, it's the new guys who don't have the domain knowledge or the expensive guys who are assholes and redundant.

This goes back to my favorite adage:

1. Be good at your job
2. Don't be an asshole
Five Huge CSS Milestones
The iPhone 8 boasts wireless charging. Expect to see this everywhere soon. – Vox
> the entire language, GUI, text editor, image programs...etc in a tiny amount of code

But it wasn't internationalized, accessible to people with various disabilities (e.g. blind people via a screen reader), automatically installing updates over the network, encrypting all communication over the network (as in TLS today), etc.

No doubt some bloat comes from accumulated incidental complexity. But to some extent (I don't know how much), one person's bloat is another person's essential features. For example, if you tell me about some bloat-free GUI toolkit that draws its own widgets (as opposed to a wrapper over multiple platform native toolkits), my immediate reaction will be "What about accessibility?".
I created a site with similar idea back in 2008 (even tried to get into y-combinator, but no luck). My big stumbling block (among many things) was that I couldn't let people cash out with out a lot of paperwork. Basically either be a bank or create 1099's for everyone. Don't you have "Know your customer" issues or does using cryptocurrency make that go away. I would not think so. May you will just worry about that later, when/if you get traction.

How about nested comments?

Looks great so far. Good luck.
Or be effectively giving a large cash handout to someone basically on the basis of happening to be around at the time.

"Doing right by those around me, even if it doesn't change the whole world" is another way you could look at it.

I agree that it seems she's a bit over-triggered by that $6 loaf of bread, at least.
This is irrelevant, because if you believe that you're at risk from your fingerprint data being compromised, you can always fall back to not using biometrics at all. They aren't your primary authentication mechanism.
In my experience, driving for both about two years ago, Lyft did require an in-person visit from a "mentor" to get approved, while Uber did not. Neither required any sort of technical inspection or mechanic check.
Course Every PHP Developer Should Take Nowadays
https://eugene.kaspersky.com/2015/03/20/a-practical-guide-to...

"For the record: I never worked for Russian military intelligence. As I mentioned above, I worked as a software engineer at the Ministry of Defense."
There is no identity without authentication. A fingerprint gives a little bit of weak authentication, in the clear, easily observed, easily forged, and irrevocable -- as bad as it gets.
Thanks for your great comments. We launched the beta only three weeks ago so it is definitely rough around the edges :) Fixing issues as fast as we can.

> Also, does anyone know what kind of regulatory upkeep a project like this requires? If a site like this operates with multiple currencies, it's essentially an exchange and probably has to register as such (they've outsourced this). However, if it just keeps user balances (not really a bank, but similar), does it have to register with any particular authorities?

We have discussed with lawyers and are sure to stay inside the law. Because all payments are p2p and we are not a custodian, the regulatory burden for us is a lot lower than many other similar projects.

> edit: your site allows a blank password, the title is "Yours | undefined" on profile pages and the menu controls to the left of the message input are very unintuitive. How do they work? Also, the profile ids are from hell:

Will fix soon. These things are already on our issues list :)
Shadowy path may lead to treasure (2007)
You could, but at Google "frontend" work means things happening in the browser.
It sounds like you are doing it right. I only personally know two really good people. One is my mentor, the other I made my business partner. Good luck.
"Reply with your prayers to help little Billy afford chemo"
See, it wasn't really a risk for me to spend 20k. Comparatively speaking, that's probably something like a minimum wage employee risking a dime.

That's the inherent unfairness in the system. I can just give 20k to my favorite charity and not even be mildly impacted. Chances are, I won't even save the receipt to give to my accountant for tax purposes. That'd buy someone a nice new car.

It's not fair. I am definitely at an advantage. Now, I earned that advantage. I worked for that advantage. That doesn't make it any more fair.

I'm not happy with the word fair, as it implies morality. I'm also far more able to help those who need it, and I do. So, from a moral viewpoint, I'm very much okay with it. That doesn't really make it fair, however.

What's Joe Sixpack going to do by investing a dime in a single go? Not much. I made enough on just Tesla to buy Joe's house, spending the equivalent of a dime.

It is what it is, but it's a huge advantage. I'm not suggesting it's morally unacceptable, just a reality. I'm not even suggesting we can change the system, just expressing the reality.
Insanely Talented Singer/Songwriter Why isn't she huge?
At a two-person startup, the front end developer is the one doing Angular or React, and the back end developer is the one doing Django or Rails.

At a mid-sized startup, the front end developers are probably also responsible for Django / Rails, and the back end developers are responsible for things like managing the Hadoop cluster and the machine learning components.

And at a large company, anything built with existing libraries might be considered front end, whereas back end might be creating a new database or whatever. I don't claim to know how Google works, but as companies get bigger the back end tends to go further back, and so the 'front end' encompasses more also.
If this is a merely negotiation problem than the problem gets stated in a different tone.

I have been told many times that I need to work on my negotiation skills. One manager has even asked me whom do I go lunch with. And why don't I go to eat with the big shots. Of course you need to act all pally and buttery, saying yes to anything they say all the while.

What they mean to say is stop expecting the system to be fair and do what it takes to win.
At Google, comp comes from how effective your management chain makes your case. It has a large subjective component.
Those two points are undeniably sound advice, simple to state, and hard for some people to apply.
Oh interesting. The triple I found used the same general idea of values that sometimes coerce to a number, but it made use of octal values instead of Infinity.
You're half right. Google doesn't hire purely frontend engineers. They have a job listing for them, but once inside everyone gets the same title: Software Engineer.

At Google, the "frontend" work also usually includes the server which serves the frontend code - this means engineers need to be not only capable at UI development, but also be familiar with the Java systems that exist at Google.

From this perspective, frontend at Google is indeed similar to a full stack role at most startups running on AWS or GCP. Backend at Google is more like working on AWS itself.
I tend to think that successful companies tend to know what they are doing better than observers.
> The code guidelines in their benchmarks represent real programming practices in those languages. They promote "idiomatic" code because it is meant to represent the typical quality of code in the real world.

This could not be further from my observations when I tried contributing. These results are neither controlled nor the result of idiomatic programs.
See: https://fishshell.com/

Source code: https://github.com/fish-shell/fish-shell
That makes sense. And, yes, negotiating for yourself is a very good skill to learn. The other person may not be an adversary, but they probably don't have your best interests in mind. So, you'll want to represent your best interests.
The end goal is a meritocracy where women arent discriminated against, and are paid what they are worth.

The current situation is not a meritocracy and it needs to be fixed.
“There Is No Reason for Any Individual to Have a Computer in Their Home”
NYTimes.com is a site I've subscribed to for years.

Yet they still serve me ads and 3rd-party tracking scripts when I'm logged in.

Increasingly, I'm becoming unhappy with this and I will soon write to NYTimes.com to complain about this.

If I'm paying for access to your website I don't want to see ads. Ever.

At the very least, make ads opt-outable for subscribers.
If you wouldn't mind, please send me $20k per year. It's nothing to complain about, after all.
> There is no number of times I can press my finger on your scanner and trick your scanner into thinking I am you.

Or I could print random patterns on gel circles I put on my finger and try until one works, which is the equivalent of your password example. (There are digital equivalents of spamming fingerprint reader values to the security chips, which in practice are faster.)

It's exceedingly easy to try a fake fingerprint, and even if it weren't, it would still be possible to generate fake signals between the sensor and verification chip or fake signals to the sensor. There's no difference here between finger prints and passwords.

> Passwords need to be changed because they can be guessed.

lol, no.

Passwords need to be changed when they're compromised -- a good password is exceedingly hard to guess, to the point we should never expect it to happen, but they can be leaked through other means.

Similarly, you leave you fingerprints everywhere. So you actually leak your fingerprint values constantly while leaking password values only occasionally. This makes passwords substantially more resistant to capturing the value out-of-band than fingerprints.

> we change our passwords regularly,

This isn't best practice and isn't what most of us do; we change our passwords when they become compromised, which happens through a variety of mechanisms. (Or when we suspect that they may be compromised.)

> Bad security advice led to routine password expiration, and that bad security advice lives on. It's still bad.

Everyone knew this was bad, and NIST recently updated their recommendations against routine password expiration. However, that has nothing to do with what we're talking about in terms of username-versus-password status for fingerprints.

> it's clear that fingerprints are closer to username than password

> fingerprints are not a password

Well, I'm glad we agree.

> But TouchID isn't going to be fooled by a piece of scotch tape lifted from your desk, so it doesn't matter.

But it is fooled by easy-to-produce prints placed over my finger based on the Scotch tape lifted from your desk. This has routinely been demonstrated with fingerprint scanners, including on iPhones.

> They are a uniquely identifying attribute.

That's what a username is, lol.

I'm going to recommend you learn more about most of these things before you make security recommendations, because you were factually wrong a few times, and made erroneous conclusions based on that.
What you have written is 100% true. Especially about the dress part. A while back I started wearing a shirt and pant to work. People, especially juniors do tend to take you a lot more seriously if you look formal and well dressed, compared to say showing up in denims and t-shirt.

But the negotiation and sales part. That's the issue. Its not easy to get good at that.
> I'll bet WordPress get's rewritten in Vue.js

I had the same thought. If that's the case, it will be a big boost for Vue.
We suspect that is not the real Stefan Molyneux. We will have flagging and moderation to deal with this soon. Also we will allow more auth options so people can prove who they are (twitter auth, e.g.)
GM and Google top the list of jobs for autonomous vehicle engineers
Honestly, a biometric used solely on a device in your possession is not that bad. It is not being transmitted or stored remotely, which would be worse. But it would have been better if it were not a biometric that was being left everywhere.
3D Face Reconstruction from a Single Image
The iPhone has a liveness test as part of its biometric.
Proponents of this approach would probably argue that non-linear arithmetic doesn't show up frequently in index computation. I don't know whether this is true or not, would be curious to see data. Based on my own experience I'd agree with it, with caveats for things like a[i%a.length] but you could probably do something there like replace % with an approximation that is linear and sound.
I upvoted this submission, as did a large number of other people who probably live in the Western world. Do you think your comment is likely to increase or decrease upvotes?
Utilities have historically had an obligation to serve based upon their monopoly in each service area. For that, they were also supposed to maintain and keep modern the tech used.

Now, Verizon just wants to jump to wireless as they've neglected the physical. They actually are in default with regards to their utility agreement with each municipality

However, greasing local politicians is too easy, and regulatory bodies are filled with Industry insiders so they don't want to jeopardize a nice payday when they rejoin the commercial side of the corrupt utility model