skysight-inc/HackerNews huggingface dataset:
It's not only the compatibility that is ugly. It's also that python 2 code has a couple of ugly warts, such as the forced arguments for super(). The only way I'm supporting python 2 with my libraries is by running 3to2 and pasteurize (future package) over the python 3 source code.

I really don't want to actually have source code that works on both, it's a pain to maintain. Although the future library should make it a lot nicer, but you still need a lot of ugly from __future__ imports as well.
Is 100% renewable energy realistic? Probably not
I'll point out that Botlzmann brains are only something you would ever think about in a universe going through a graceful heat death rather than the equally likely big crunch or big rip scenarios.
There's this: https://www.mecabricks.com/en/workshop

No integrated purchase though.
School Safety Tips and Statistics for an Active Shooter Scenario
Modular nuclear energy:

http://www.nuscalepower.com/
Whereas some people will object to any security measure on the grounds that "terrorists aren't a threat".

But if we actually followed their advice, terrorists would be an enormous threat because we'd take no steps to protect ourselves.
In this case the prior salary is used for anchoring purposes, by the expectation that the new salary should not be too much higher than the old salary.

They're basically using it as a means to sanity check and calibrate their own assessment.
I am horrible at checking my comment replies, so sorry about the lateness. Hopefully you see this.

This is a fair point, but I simply want to point out that was half the reason I suggested it. Learning how to fail :)

I very much understand the mental aspect here though, so that's a tough one and my advice is not for everyone. I will say that at some point in your career you will fail though - or you aren't pushing yourself very hard. I believe this was one of the harder things I had to "train" myself to deal with; the mental load of failing at something and how to recover.

If you're not in a mental space to make that experience a positive for you? Absolutely skip it.
Most 'callback hell' situations are really just poor code structure. Easily solved with separated named functions.
Yes, there's a whole book about this, Women Don't Ask: The High Cost of Avoiding Negotiation.

https://www.amazon.com/Women-Dont-Ask-Negotiation-Strategies...

> Yet, as research reveals, men are four times more likely to ask for higher pay than are women with the same qualifications. From career promotions to help with child care, studies show time and again that women don’t ask–and frequently don’t even realize that they can.
The one cost of purchasing a home that often shocks first-time buyers
If this is text only, maybe it will work on Bash on Windows?
Yes, I find it hard to believe. You might have gotten that from when I described it as "quite unlikely."
I dislike employers who take advantage of employees.

I dislike New York City's solution too. There are other ways to empower employees and not asking about past salaries won't eliminate the pay gap. But I'm not an expert so maybe this is a step in the right direction and can result in lasting changes.
> Certainly there are people who want to blow up bombs all over the US.

Is there? How do you know this?
The second sentence mentioned the reason. Privacy does matter. It's in the Bill of Rights. And it should matter.

But like every right, it has exceptions. One exception we mostly agreed on, until recently, was being searched when crossing the border.
People should avoid using callbacks as they invert the chain of handling function calls. Rather than getting a result that you can work with, you move the logic into another function. Promises compose much more cleanly than callbacks do resulting in generally easier to follow code.

If you call function x with a callback you either handle it immediately via your callback or you have to use some other paradigm to make it compose with other async code. You get no return value allowing you to write code that looks synchronous and forget about the beauty of async/await you've completed abandoned it with callbacks. If you use Promises you can do as you wish and combine them as you wish as they hold values and you can use them multiple times trivially with other Promises,
I recently had a discussion with family about nuclear energy. One member was worried about it because the plants would be targets for foreign attacks. I told him we already have plenty of plants operating that could be attacked. Then I quickly pulled up a list of all the nuclear plants in the US. There's already one less then a hundred miles from his home. He still wasn't convinced.

I think a lot of people have irrational fear about nuclear and nothing short of a miracle will change that.
3 requirements management tips
Here's one argument: the logic changes if the data is universal.

The usual complaint about asking for salaries is that it's a trick to underpay new hires - you can give them the lower of your normal salaries or a 10% raise. That's because they don't know what they're worth, but you know what they got before.

If everyone publishes salaries (and they already do in practice, thanks to Glassdoor), that trick goes away. No matter what your previous salary was, you have leverage to say "look, you pay everyone else double that, cough up". So the primary objection to asking for salary is negated.

I'm not sure the logic is totally sound - some people will end up moving from published to unpublished employers - but I think there is a distinction.
The thing you might leave a job because you really, really disagree with that assesment!
Saying "Yeah it's sort of like religion all over again just in a different context" is sort of like a religion, but in a different context. It seems that making grand dismissals is more or less inescapable, and in the end we get really nerdy about it, and use atheistic language while we make our psuedoreligious grand dismissals.
Same. Nilay Patel and Mossberg have a great rapport.
Agreed, in the Midwest they're building new 2,500 sqft. homes every 6 months around here. (Quite poorly BTW)

Every 5 or 10 years an entirely new development emerges.

Any hindrance occurs to municipalities without room to grow. And for city zoning, it doesn't appear they have an issue "building up" instead of out.
The balance of power during an interview is often very much on the side of the employer. So I am happy if that balance gets shifted the other way a little.
Come on. It's not even difficult to find examples of non-political speech being protected.

https://en.m.wikipedia.org/wiki/Virginia_v._Black

https://en.m.wikipedia.org/wiki/Ashcroft_v._Free_Speech_Coal...

You can find a big list of free speech cases here. Many cover non-political speech.

https://en.m.wikipedia.org/wiki/List_of_United_States_Suprem...
Google updates Material Design Guidelines, releases color tool for palettes
If you are porting from 2.7 and don't require compatibility with earlier Python versions, then "future" [1] is a better, cleaner alternative to six.

[1] https://pypi.python.org/pypi/future
> it's ridiculous to claim that the US has taken terrorism less seriously as a military objective than the UK took theirs

Then what was the point of saying that the Brits had rules for golf during the Blitz?
> moving from native clients to essentially a bundled browser

I'd argue that this is a better choice than having to develop and port features to all their different platforms. By having their clients be a web view they're able to offer features / innovate quicker.
Only artificial recursively self-improving super intelligences know the answer
The obvious consequence of a company publicly posting salaries (or even having clear salary ranges that nearly all the employees at the level of experience fall into) is that a thorough recruiter doesn't even need to ask your previous salary to be able to use it as a benchmark to work with though.
I'm surprised by how many people didn't see this coming. Rules are intended to weed out undesirables, for whatever reason, even if not objectively moral.
Yep. I find that in the US people are very reluctant to discuss salary amongst themselves, which makes it super hard to figure out if you're getting screwed or not. Europeans tend to be much more open about their earnings.
I've used both Polymer and Vue for a few projects, and Vue's single file component method, coupled with WebPack, is almost identical to writing an app with Polymer.

Except that Vue doesn't ship with all the Polyfill baggage that Polymer does. Polymer has came a long way, but it still feels slow on anything but Chrome.

Once the Web Component spec is finalized, and built into browsers, I think Polymer will be a great choice. Today though, I gotta give the nod to Vue.
I was recently in Madagascar - it's not uncommon to be driving while sipping a beer, or driving home at 3am after drinking since 9pm.
I theorize that they must just sweat it all out.
Eating while drinking helps, too.
Some confirmation that this isnt fake:

http://kfrankc.me/cs88s/ links to the same form.
https://github.com/kfrankc?tab=repositories includes a photo of him and links to the same kfrankc.me

https://scholar.google.com/citations?user=v2iJEd8AAAAJ&hl=en
Links to the same kfrankc.me

seems legit.
So far we seem to be objecting to the wholesale copying of phones, aggressive physical inspection of women with back braces, and the frisking of children --- each of which you've defended as vital to defending against the terrorist threat.

I feel as if you might be making my point for me.
In another words, it's all good.
How Pharma Game the System to Keep Drugs Expensive When Patent Expired
"We want to help people stop forgetting 90% of their lives."

I also saw this tagline or similar on PH, and I got to say I'm not a fan. If you look at everyday on it's own, for most of us, it's pretty boring stuff. Why would I want a record of that? If something hugely important happens, sure maybe I'll want to be able to access that memory / my thoughts at that time in the future.

But 10 years (let alone 50) from now, I might not even know what year big events happened. And so I'll be digging through maybe 100s of hours of recordings/text if I'm looking for a specific event.

There's definitely some product in this space that could be great, but I don't think 60 second recordings is it, especially without some way to filter through the boring crap. I imagine looking through my old calendar would be more helpful than my 60 seconds of nightly drivel.
I don't think I've ever seen public salaries at places that pay on the lower-end. Usually I've seen it with startups that pay fairly well, but I could be wrong.
All of the Open Enterprise Server stuff, which is one of their big moneymakers.
Obviously, that regardless of what our military might be doing, our societal and public policy responses to this threat have been comparatively juvenile.
Do laws against fraud violate freedom of speech?
Muslim man dies after attack by Hindu 'cow protectors' in India
It's all about information asymmetry. The employers have information you don't so you can't use that information to your advantage in negotiations. They really don't want that information to get out so they can continue to push salaries lower.

The only reason they want to keep that information private is to use it to their advantage.

I believe, last time I researched this topic, is that transparent salaries tend to increase pay across the board and make pay more performance based rather than negotiating skills based.

EDIT:

http://economics.usf.edu/PDF/Asymetric%20Information%20Porte...

> Beginning in 1989 the National
Hockey League Players’ Association began annually to reveal the salaries of all its members. Over the next five seasons as contracts were renegotiated wages rose precipitously. Over the same period the role of player performance in determining wages gained importance while the identity of the team with which they negotiated lost all
significance.
This actually sounds like a good use for WINE. If the DLL has few external dependencies, it could probably be made reliable enough for mission critical stuff.
> Plus, it saves a lot of wasted negotiation time on both sides if your price is just way too high for the company and this is clear from the beginning.

This. I'm very upfront that if a company can't meet at least a particular dollar amount expected, it's not worth wasting both of our time. This saves a ton of time, and also serves as a nice red flag when a company agrees and then later tries to negotiate down at the last minute (if they're going to penny-pinch at the last minute, things like bonuses and vacation approval are basically never happening).
You may want to look into this “Reclaim Windows 10” Powershell Script:

https://news.ycombinator.com/item?id=13344318
I never consider interviewing and negotiations a waste of time. It's very valuable practice, no matter what the outcome. Practice is how I get better at both. The more interviews I go on and the more times I negotiate salary, the better I get.

Also, even if a company can't hire me at the moment due to real budget constraints, they might be able to do so in the future, or perhaps one of the people I interviewed and impressed enough to get to the salary negotiation phase will remember me when they move to another company and want to hire me then.

If I name a number way out of their range first, though, they could reject me right off the bat, and I'd never get an interview in the first place, never get the practice, and never get a chance to impress anyone. All of these are worth more to me than the chance of a salary negotiation going sour because I wind up being too expensive. Besides, I'll always have the chance to decide whether I want to work for the company despite them being below my ideal salary. Salary isn't everything.

As for anchoring, that might work if you're negotiating with novices, but many employers have professional salary negotiators (either HR or recruiters themselves) who know about anchoring, and they're not going to get fooled by such psychological tricks. If I don't reveal a number first, however, they are forced to name one, and then the ball is in my court, and I can negotiate up from there as I see fit. There's really no downside.
If you can't say anything nice, don't say anything at all...
ps, not directed at you. but more an extent to what you said.
I qualified my comment by stating that I agree with the parent as far as current salaries go, yet that in the general case of salary expectation discussions it is nevertheless a better strategy to state a number first. IMO it isn't clear from the parent that they believe it is a good idea to disclose any number first (whether expected or current salary).

BTW, if specifically asked 'what is your current salary?' I would typically respond with 'my ideal new salary is $X'
> I never answer questions about my past salary, not to employers and not to recruiters.

You answer it by accepting an offer or giving a ballpark number for negotiations.
Interesting, could well be. So not a problem for people on the ground, but you'd want to have a good noise-cancelling headset while on board.
Swap out prophets for celebrity "scientists"/eccentric billionaires, and swap out scripture with speculative pseudo-scifi publications, and you have a new religion!
Whatever exception you make - for children, for back braces, whatever - will be the exception terrorists will exploit.

If terrorists know you don't search children, they'll place bombs on children.

It's little use locking the front door while leaving the back door wide open.
Fake news is "Hillary buries dead FBI agent under pizza restaurant."

Misleading/sensationalized news articles are just normal "news", as judged by the past 200 years.
Hijacking this for visibility.

If the recruiter asks repeatedly, a trick that I learned is to answer that it's in your employee confidentiality agreement not to discuss the terms of your employment. It's arguably a true statement as well (in case you were concerned about telling a white lie)--your employer could be considering your salary as confidential because they obviously haven't disclosed it publicly, so you are taking a very conservative approach on the confidentiality terms in most contracts.

edit: the statement doesn't need to be legally defensible, it gives you an opportunity to redirect and ask what they are willing to pay for the position or to learn about their benefits package.
http://www.npr.org/2015/12/10/459100751/utah-reduced-chronic...

Great success. Do some research. Spend effort expanding programs that work.
Really? What genre of music do you listen to mostly? I enjoy hip hop / rap style music and the discover mixes are generally pretty awful. They seem to just throw in a bunch of popular radio hits and some b grade tracks from smaller artists. I've been really disappointed because people always talk about how great the discover feature is.

I have much better results playing a full album on youtube and letting youtubes auto play feature pick the next album for me. I've discovered a half dozen artists that way on the last year.
Why not? That's how markets work. When I put a market or limit order in for a lot of stocks or grain futures or forex options, I don't haggle with the market: I (electronically) compare my options and simply take the best one.
This is easy to say but hard to do in practice. Every JS application I've seen in production is littered with callback nightmares. It might be possible to avoid but in practice it's too difficult.

async makes it easy and I don't see a downside to using it everywhere possible.
Unfortunately there are employers in NYC who do call previous employers to verify salary. Remember that most white-collar employees are in much less demand than developers and have to deal with far more employer bullshit.
Here's the change log linked from the downloads page:

https://raw.githubusercontent.com/chapel-lang/chapel/release...
Looking at the setup.py they only depend on tensorflow and some testing thing which both seem to support Python 3 just fine.
Amazing people can listen to that 10x fast audio reading of the characters on the screen and manage to play the game like that.

Hearing the audio I could barely even keep up with it. It's like watching two people play chess entirely in their heads.
The Mathematics Behind Gerrymandering
I think Google tried something like that, with mixed success. I think that firms should actually do IPOs in multiple incremental steps.
Hi, I'm one of the cofounders of Clerky... we started this whole rise :) Out of curiosity, what is the "sort of" part?
Tell us how good sales works.
Callbacks are simpler, easier to understand and explain. 'callback hell' is usually the result of 'poor code structure' that get's fixed with separated named functions.
Employers ask for your salary to make sure it makes sense to talk.

Everyone mentions it to be lowballing you. But what do you think happens when you mention a higher number than they expect?

While it sometimes will end the conversation (because they're unwilling to pay), sometimes they'll match that, leading to a higher salary than what the offer would have been.

Of course, often, including in big companies, the background check isn't done by the hiring managers. So you can straight up lie about your salary, get a higher offer, then when they background check they get the real one, and they're none the wiser ::shrugs::

Even without lying, In the couple of occasions where I was underpaid and trying to go up, it's simply what I would say when asked. "My salary was X, but I'm looking for X + Y".

It's just not that hard.
Has anyone run into issues for sharing a current salary that anchors the discussion too high? I could see how an employer might pass on a candidate who's actually interested in the job, just because they know they can't match what the candidate is currently making and it's likely a waste of time to spend hours evaluating someone who's making 50k more than what you could ever offer.

Or is this purely theoretical and not seen in practice?
It's one of the primary goals of the project

> Provide low-level buildings blocks for pthreads-style shared memory: shared memory between threads, atomics and futexes (or synchronic).

New atomic memory operators, including loads/stores annotated with their atomic ordering property, will follow the C++11 memory model, similarly to the PNaCl atomic support and the SharedArrayBuffer proposal. Regular loads and stores will be bound by a happens-before relationship to atomic operators in the same thread of execution, which themselves synchronize-with atomics in other threads. Following these rules, regular load/store operators can still be elided, duplicated, and split up. This guarantees that data-race free code executes as if it were sequentially consistent. Even when there are data races, WebAssembly will ensure that the nondeterminism remains limited and local.
Awesome Artificial Intelligence (AI List)
If only press said idiots instead of terrorists when they covered stuff like this.

Why give any kind of credit to these idiots?

Don't blame some religion for what idiots do, don't blame people from other countries for what idiots do.

Education and general life improvements can help idiots to become non-idiots.
Closing borders or checking body cavities seldom help with that.
Moving beyond regression or differential equation modeling for dynamical systems
You mean why N26 doesn't do that already ?
> Download 1 GiB to render a document? Probably not.

Any day now we'll be downloading 1 GB in order to read an article, so just give it time …
A ten-minute introduction to the Y Combinator
The best way to see if your company is willing to give out salary information to random verifiers, is to ask HR yourself.

In most cases they would not give out that sensitive information unless they have a written consent specifically stating that you allow salary information to be given.
Anchoring only works if the potential employer is ready to buy. Many, many organizations will simply use the number as yet another filter, and you won't even begin discussions.

By giving a number first, you're either too high and you won't have an opportunity to sell yourself, you're too low and you've literally already negotiated against yourself, or you're lucky and right at their expectation, which you could have gotten to by simply not giving the first number.

I do agree with the wasted negotiating time thing.
When r/place was running, things divided into factions as art was placed, and subreddits were even formed dedicated to creating or maintaining a piece of artwork. There were a _lot_ of people, myself included, who really enjoyed being able to do their little part to create something bigger, or maintain it. It was only running for a few days, and was new and interesting for a lot of folks.

Not to say there weren't bots, but keep in mind you could only place one pixel at most every 5 minutes, per user, and that new users weren't allowed to place pixels at all, to discourage people from amassing users just to draw things.
The objective of terrorism is not to kill. The objective is to induce fear.

If you do not take a balanced approach at protection, you risk losing out the mind war. The result? The US becomes a closed country, no longer the land of the free much less the brave. The ultimate goal of terrorism is achieved.

My reference for correct behavior towards terrorism is the UK during the IRA campaign. Security was handled as a serious affair, but as silently as possible. Some fatalities were deemed innevitable, and reported as such by the media.
> A similar approach was first tried in Los Angeles in the late 1980s and New York City in the early 1990s.

> Later, the Bush administration adopted the model, and cities and states started writing 10-year plans to end chronic homelessness.

...

> And even though many cities in the U.S. have also been doing this for a while, they still come to Utah to study why it's working so well here.

The article mentions several times that it's already being done. This isn't mutually exclusive with efforts to fight terrorism.