skysight-inc/HackerNews huggingface dataset:
The #1 most important thing for these salary's is to signal competence. Actual competence is far less important.
this advice runs against a lot of the usual recommendations about ignoring what people say and focusing on what they do. It may well be that basing price on what people say they'd pay results in leaving money on the table.
2FA is something you know and something you have.

So fingerprint gives you part 2 and password gives you part 1.

No need for an additional MFA device.
> Now there is probably some salary inflation going on here where people are counting compensation that is restricted over a few years as though they earned it all in the current year.

I've actually found that people tend to be very careful about counting $600k in stock over 4 years as $150k per year.
The point is that it doesn't matter what the typical person will do. All that matters is that somebody, somewhere reverse engineers the EFI binaries, and that it's easy enough for normal people to run a program to check their current EFI against a whitelist of known good EFI binaries.

This is a banal point, except: if the threat is that Intel (or some other huge vendor) backdoors their EFI binaries, it will get out that they did so. It's not "the perfect crime"; it's practically the opposite of that: one guaranteed to be detected, and that will exact maximal damage on the perpetrators when it gets out.
Flocker is a giant beast, now I need one more big dependency and start generating client api certificates and so on.

I had one problem, now I have 2.

It should be as simple as specifying the driver in compose,
maybe with one apt-get install (or equivalent) command to install the driver, though I content Docker should provide such basic driver directly.
Pancake wants to bring Rust into Radare2
Windows 95 Defrag Simulator
Librato/Papertrail | SF| Sr Data Engineer | Full-time / Onsite | http://solarwinds.jobs/san-francisco-ca/sr-data-engineer/AE5...

We're looking for a full-time software engineer to take a key role in building the scalable backend systems that power Papertrail.

Qualifications:
You are an experienced Internetcentric engineer, equally adept at improving interfaces as at tracking down complex performance problems
At least 5 years of experience building distributed systems with Java or Scala
At least 2 years of experience with Ruby
Comfortable with using and reasoning about concurrency primitives
Experience with ZooKeeper, Dropwizard, MySQL
Understand the importance of metric instrumentation
Experience with building and consuming REST APIs
Comfortable debugging network, disk, performance issues in complex distributed systems
Experience working in and developing for Linux environments
At least 6 years of relevant engineering experience
Comfortable with cloud-based deployment, remote teams, and git

What's in it for you?
Competitive salary & compensation
Excellent health care coverage
Fewer meetings, more shipping. Most of Papertrail’s operations are in Slack.
A team committed to life/work balance
4% 401(k) match

About Papertrail:
We're part of SolarWinds, which includes Librato, Tracelytics, and Pingdom . You can see some of the things we think about on @papertrailapp.
SolarWinds is on Forbes' lists of Most Innovative Growth Companies and America's Best Small Companies.

If interested please apply directly or email me at ashley.gerwick@solarwinds.com and reference this posting!
> Split it into several programs that can be verified independently.

Doesn't help if the correctness of the whole program relies on an interaction of the component. See my blog post on the matter (the complexity of verifying a composition of k components is not only exponential in the number of components, but in the complexity of each; in other words, internal complexity cannot be hidden; this was proven in 2005 I think, by noting that the interaction of k finite-state-machines can simulate a nondeterministic Turing machine with a tape of size k).

> Frankly, I can only see this as a good thing.

Many of the algorithms that drive most progress in verification itself -- such as SAT solving and static analysis -- would themselves fall far short of this bar. Ironically, forgoing complex algorithms altogether would make verification even harder.

> This comes from the assumption that you first develop the system to be verified and only then verify it.

No, the two problems are of the same complexity. Developing a correct program can be no easier than verifying one. See my post.

> As if more software were automatically a good thing.

Well, that's a whole other discussion. In this one, I do not attempt to judge whether software is good or bad.
We should always look for the simplest explanation but be willing to acknowledge and embrace our ignorance too.

Your attitude turns people off science; it's a plodding, unimaginative attitude that pours cold water on every novel idea without even bothering to explore it properly. The history of science is full of discoveries resulting from accident or whimsy, and I think speculation is an important exercise. Nobody ever got to the top of a mountain by meticulously documenting every step of the route.

So there's a risk you'll pin some hopes on an idea that turns out to be wrong. That shouldn't be bad for your career unless you do it all the time. A scientist who is never wrong about anything isn't taking any risks.
That's like asking "What is the highest salary that a pro basketball player can make?" And it has the same answer: whatever you can negotiate.
Do they, now? From the abstract we only read that (according to the authors) there is some kind of consensus:

Consensus is particularly strong for propositions of free international trade and capital flows.

But as to what that consensus (in particular, as to whether the effects of free trade are "good", "bad", or "mixed") -- we would need to dig into the full text of the article, which is available only to subscribers.

And anyway that "consensus" was from 2003, and a lot has shifted in the universe since then -- particularly in regard to the question of whether free trade is still a pretty neat idea, or not.
Accept his PR. Now fix the code yourself with all your review comments in a new PR. Test. Commit. Checkmate.
At least you can put a strong generated password there!
I remember hearing it from Steve McQueen in The Magnificent Seven when I was a kid https://www.youtube.com/watch?v=V7GP3l5znc8
I may be mistaken but my understanding was that touch panels can't reduce glare as effectively as non-touch because they need oleophobic treatment in addition to anti glare treatment, and this is why MacBooks of all flavors have better glare mitigation than touch-equipped laptops.
Same story was just posted a few minutes ago:

https://news.ycombinator.com/item?id=13841366

(Also, that article had something somewhat interesting to say about the video. This one does not.)
(Note: cofounder responsible for pricing decisions many times.)

The closest thing to a "methodology" I've found is asking these four questions and having the users generate their own pricing curve [1]:

Here's a real set of curves this process generated for me recently: http://imgur.com/lPKLk53 ($ values redacted)

The four questions are:

1. At what price would you consider [the product/service] to be so expensive that you would not consider buying it?

2. At what price would you consider [the product/service] to be priced so low that you would feel the quality couldn’t be very good?

3. At what price would you consider [the product/service] starting to get expensive, so that it is not out of the question, but you would have to give some thought to buying it?

4. At what price would you consider [the product/service] to be a bargain—a great buy for the money?

Require a specific $ amount as the answer to each question.

Take ~100 users, ask them all four of these questions, and then compile the results. You really have to do this on a subset of your own qualified potential customers to get any meaningful data.

The neat thing about this is that this creates a price sensitivity curve without anchoring the interviewee with any prior numeric values.

At the end of the day, it's still a gut call about where to place your price point relative to the user's alternatives, and testing is encouraged, but these four questions are a decent start.

[1] https://en.wikipedia.org/wiki/Van_Westendorp%27s_Price_Sensi...
Actually lunar orbits are considerably less predictable than that: https://en.wikipedia.org/wiki/Gravitation_of_the_Moon
It depends on how much skin in the game you have as a reviewer. If you have to or will have to maintain the same codebase (sounds like in your case you do), then you have every moral right to reject the code and refuse to ship it. If you're literally not allowed to reject the code, escalate to your common manager. If it goes wrong later, at least you're on record objecting, and this could also be a signal to get a new job if your manager can't even handle this.

And if you don't have skin in the game (ie, process just requires "someone" to review it even if not on the same team), then whatever, give them the advice and let them burn themselves if they wish.
100 Announcements from Google Cloud NEXT
Use good invoicing/billing software that allows you to discount on a per customer basis.

Start with two price points: one targeted at price sensitive customers, call it price A, and one targeted at price-insensitive customers (think enterprise), call it price C.

Set price A lower than you think - you can always add features and raise later to the point that people start to scream.

Set price C at much higher than you think - use volume discounting to offer discounting where needed, but this is your anchor point for conversations with big customers.

Consider whether price A is your acquisition channel or if you will have a "free" tier. If you don't have a free tier, you can feel fine with a lower than optimal price for tier A, as this is your conversion channel to price C.

Eventually you'll want a tier between A & C (call it B) to anchor pricing and encourage people to choose A or C. Refer to research on movie popcorn prices.
It's either a ton of people and they don't want to admit it OR it's very, very few people and they don't want to be asked the obvious follow up question of "who are they?"
This looks great. Can you do custom designs as well
Yes, that is the (correct) implication. GnuPG isn't "freemium".
They used to post total compensation for the computer programmer role and they were lower than Google was paying at the time.
Agreed.

"Not exceptional in any manner" seems like a bit of an out-of-whack analysis of a $250K engineering salary at Google.
Except Planet's goal is global scale, and I don't think they are aiming to do anything real-time atm.
That's pretty apt. There are always legitimate reasons why doing something is difficult and imperfect, but there's a really clear future here. It's absurd to think that Visual Studio will remain 32-bit in 10 or 20 years' time.

And no, as any C++ developer will tell you, the answer is not to move to a souped-up text editor (Visual Studio Code).
I really doubt that multi-thousand-dollar dental events are as common as once every five years.

Insurance doesn't have to be for things where most people will never incur the expense. The average time between car accidents in the US, for example, is a bit over a decade, yet car insurance is very much a thing (and not just the legally mandated liability insurance, either).
Isn't it unlikely that an individual engineer (or even a handful) could effect a design level compromise on such a massive project as building a processor? Not only because of the managerial oversight they'd have to circumvent, but because of the overall system complexity. As sibs have pointed it, it would seem much more practical to just compromise Intel at a corporate/managerial level.
I took the post to mean $250k was the low end of the range for highly compensated programmers.

Something more like $150k or $180k is probably a more realistic mid-career average compensation (with salary somewhat less than that, in the USA).

Complicating the discussion is HN skews to the high end of the range. Not only is it very SV-centric, the type of programmers who post here appear to be atypical (high performing, entrepreneurial, etc).
> That's a pretty crappy perspective. If you don't like the terms, negotiate.

Sometimes reality is crappy. Unless you're a legit famous person, most of these Bigcos are not going to adjust the terms of employment for you.
This is a problem that a good project manager and the company's development culture can solve. Ops also frequently has things they need from developers but rarely get.
"A man can never drink his fill by waiting in line for the tap"
-- From Breaking Bad
When you download the imagery, the data is in UTM rather than Web Mercator.
I've had a few doors spawn along walls with seemingly no purpose..or is there? Bug/never got around to anti-door-logic-placement in 7days?

Anyways, great game and well done. Shared with all my friends!
Is it possible that AMP pages are preferred because they're a better user experience?
Opioid abuse is not supply side limited.
> I'd be afflicted by the same sad disease as you, lack of imagination.

And the conversation stops here. Thanks.
It feels like Trello was a HUUGE SUCCESS. Todo lists are notoriously hard, and target a very thin demographic; people who are trying to plan and track progress, i.e. middle managers or OCD contributors.

Reaching $N million instead of $2.4N million, where N > 200 doesn't really feel like an obvious shortfall.
It does not magically split one connections into many. One domain == one connection. Sure it won't undo your "domain sharding" hacks and merge your CDNs, yeah :)
New NASA Radar Technique Finds Lost Indian Lunar Spacecraft
No. You will pick up your checked baggage before being diverted to a search area at the exit, where openly Trump-supporting CBP officers will, after violating the Hatch act, treat you like shit, ridicule and attempt to humiliate you, rummage through your stuff, and intentionally leave it all a mess for you to repack.

While it's unofficial CBP policy to harass in any way possible--the more petty the better--citizens who refuse to answer questions, I have not yet experienced a device search, so this is just speculation; CBP might just get your checked bag(s) and demand your assistance while you're in the main secondary detention area.
I think we've been with HelpScout for around 4 years at https://openexchangerates.org. The service is great, and they just seem like a really honest, switched-on team.
These articles are correct and $250k is not exceptional for a few years of experience. They are talking about total compensation and not salary. If you think this is exceptional then you owe it to yourself to respond to some of those LinkedIn messages. And, no, this kind of pay is not restricted to NY/SF/SV/Seattle.
Thanks, I corrected my response. Was I partially correct about the gaseous reflective coating helping to smooth over any micro-imperfections?
Right, but simply saying, "that's the way we do it here" doesn't communicate all that. Hence, "that's the way we do it here" is not a good reason. "That's the way we do it here, and here is why we do it like that..." is how it should be phrased.
"No man on Earth has no belly-button"
Hey Finbarr! Is this related to our chat? :)

Even if not, some great advice here! Thanks! ...but I think most of it is B2B focused primarily. I'm curios (and can't find much info) about subscription pricing for consumers in particular... And especially for products that aren't as wide spread as Spotify or Netflix.
Google Cloud Announces Machine Learning Startup Competition
Airbnb Nears Approval in Room-Starved Japan with Tighter Rules
Economist here: other than doing a field test with a given price (break even + some margin determined more or less ad hoc) you just set a price and see what the market says. If too low you'll sell a ton, if too high you will sell few or none.
and.... what alternative could you possibly have? There's a reason the Russians reportedly moved to typewriters.

https://www.theguardian.com/world/2013/jul/11/russia-reverts...

The entire computing ecosystem appears to be P0wned by various intelligence services. And, its not unique to the CIA or NSA. The Chinese are assumed to have backdoors into most of what ships from their country.
You can do surveys. You can call potential customers and ask what they would pay.
It's not exactly what you're asking for, but you'll run into a big one in about two decades.

The only other example I can think of is the general "problem" of large databases. There's just a lot more paging and churn that has to happen in a 32-bit address space. Many NoSQL databases in particular have a memory model of mmap'ing an entire database, which runs into a hard limit on 32-bit address space.
Conjoint analysis is also a common approach. It requires less specific answers from customers about price points, which people are often unwilling to share.
Long Read: Leveraging ReactJS in HackerEarth Assessment Environment
Indeed, but it does probably takes a bit of time before you're proficient enough to be worth that amount. Plus, the time you spend working with this tech, is also a time during which you're most likely not learning something new.
I'm on the 4th floor but can't seem to go up the stairs to the 5th floor?

A staircase leading up is here.

And I press '<' but no go.
Maybe the cost is not completely prohibitively expensive but they do consider it a premium feature. Have to earn money :D
Only way to achieve that is:

- working on a project that requires highly specialized training

- working on a project that is hard to replace

- working on a project that is critical to the well-functioning of the core businesses of the company

- being a good negotiator

- having the patronage of management
I think that in some cases, it can even be helpful for source code.

There have been a couple of times where I wanted to understand how an interesting library or bit of code worked, so I printed the code out and made notes right on the page as I read through it.

I'm sure I could have accomplished the same thing digitally - but for some reason, the knowledge seems to 'stick' more quickly when I'm writing out the notes physically on the same page as the code.

IIRC, one of the developers in 'Coders at Work' liked to print out code he was working on to help him develop an understanding of it. I think it was Josh Bloch, but it's been a while since I've read the book.

All of this is also anecdotal, but I think it's worth a try for anyone who hasn't. It might be useless for most people, but I believe in experimenting with different ways of absorbing information to find out what works best with your brain.
A recent thread on find the pricing through experiments: https://news.ycombinator.com/item?id=13756302

They recommend Amplitude if you can't build everything yourself. They say it lets you have cohorts and compare behavior between cohorts, so it probably helps compare common metrics. I don't know if it makes suggestions for experiments or helps to run them.
We use MemSQL and it has the best replication setup process for any relational database with 1 line:

REPLICATE DATABASE db_name FROM master_user[:master_password]@master_host[:master_port][/master_db_name]

Why is it in 2017 we still don't have any other database that can come close to this? Basic replication is very well understood and used everywhere but it seems like database creators just don't understand what should be prioritized.
Very sensible approach. My question would be: does this product make more sense as a recurring subscription or a one-time cost? Perhaps so many things are subscription based now that it is hardly a question, though.
I like it! One annoying thing I noticed is that if you kill something while it's in a doorway, you won't get any loot from it. Maybe things could stack on open doors?
Composing music in AWK
> could your Solaris (mostly) seamlessly connect and disconnect to wireless networks? I don't even think there were that many wireless networks in the world back then :)

Let alone USB. During my training, there were lots of desktops running Windows NT 4.0, which did not know USB. By the time I had already become so used to copying data back and forth with a USB thumb drive (even though back then their capacity was still measured in megabytes), that it became fairly annoying to walk up to some computer, plug in the thumb drive, then realize this machine is running NT 4.0, not Windows 2000, cursing, then looking for another way to get some piece of data on that computer: Usually put it on some other machine copy it over the network.

Ah, those were the days... ;-)
Look at /r/programming, do you think these people are pulling $250k. They are closer to the average. If you think $250k is normal you're in an exceptional bubble.
>Most of all, that she was essentially turned into a criminal through the failure of the state.

Yes, and that failure is the arbitrary criminalisation of certain narcotics.
And people wonder why everyone wants into the industry... alas it's top talent that command these salaries, I'm far from there. Qureshi's story is a fun one I've heard him talk about it on the Software Engineering Daily podcast. Knowing how to negotiate well and being a talented engineer can go a long ways.
The ToS that you're presented with upon signing up is pretty absurd. It requires you to commit to providing feedback "on a regular basis of not less than once each week during the Beta term", and to creating "a written evaluation of the functionality, performance, usability, and stability of the Beta Site and documentation provided."

It also prohibits you from linking to the site or disclosing any information about it, including the existence and contents of the ToS. Boy, I sure hope I don't get sued for posting this comment. /s
I suppose there may be some sort of anti-hacking law that could be twisted to fit this case, and if the cops came to my door over it I'd definitely hire a lawyer before I said anything. I somehow doubt if I'd be charged with a felony for accessing an account that is registered under my name and email address and turning off email notifications, especially since I've tried everything else I could think of to stem the tide, including emailing support, etc.

Plus, this individual who keeps signing me up lives in Australia. I cannot imagine our system is so dysfunctional that both the United States and Australia would agree that a) this is a criminal offense, and that b) it would be worth going through the effort of extraditing me to face justice.

I mean, I haven't even received another password reset request from those websites I logged in to fix that issue, so I half imagine that person is using my email address as a plausible address for email they don't care about.

I understand what you mean, but I don't think I'm going to have to spend the rest of my life looking over my shoulder. The few personal emails I've gotten with financial details (gym membership bills, etc) I've responded letting them know about the mix-up and they've been more than happy to fix the issue. Feel free to say I told you so when I end up in a jail full of kangaroos though.
I just saw this week an endocarditis due to the lack of dental hygiene. None of us was properly trained to evaluate if the patients​ teeth were ok. Shame. Dental health is not even available in lot of public health system like the Spainish one. I'll never understand why it's treated differently.
It's also insecure to have password rules because people end up writing, printing, saving passwords in Google Docs, because they can't remember them anymore with those stupid rules.

Totally agree about the "security questions". They're just insecurity questions. Everyone knows what street I used to live on and what my previous phone numbers were.
Top 1
Does anyone know of any remote companies that pay even at the lowest end of this range?
https://github.com/search?q=correcthorsebatterystaple&type=C...