skysight-inc/HackerNews huggingface dataset:
This is really good news. Plaid has an amazing API, it makes it very easy to get your own financial data. I'm trying to analyze my own spending habits / make a budget-allocator using my own patterns, so it's been insanely helpful. My big fear with all small SaaS's if they just suddenly shutter, so a new round of fundraising is always good news :)
TL;DR: low denominator.
They ask you for code. Real, runnable code. The interviewer types it verbatim from what you wrote on the board...

I don't think they necessarily care if it compiles, or if you forgot whether it was Set.has() or Set.contains(), but for some reason they do not allow pseudocode.
All Hail the New Docker Swarm
There is definitely a gradient of severity with "reckless" driving.

Have you ever driven full speed through a red light? Sat at a complete stop of a freeway in an attempt to merge in to traffic? Taken a U-turn on a freeway? There are things that don't cause an accident, but once a driver does, they should probably not be allowed behind the wheel for at least a year, some things possibly even a lifetime ban or some additional evaluation.

There is an interesting dichotomy because smart phone usage has really caused a big problem with distracted driving. Even Geico experienced an increase in claims last year, and I suspect this was why. When I watch traffic sometimes over 50% of drivers are looking at a phone screen rather than the road. At the same time, mobile sensors are enabling something which will end with roads being extremely safe and killing very small numbers of humans a year.

There is a lot of talk about privacy and freedom on the internet. Privacy and freedom on the road is dead in all dimensions. You won't be anonymous, you won't be able to take go somewhere when the police/authorities are looking for you, there may not even be private ownership of any vehicles in the US in 10-15 years.
Change the loop counter? That's supposed to be impossible in Fortran, isn't it? Maybe that's a language extension?
The fact that there isn't yet a 400-lightyear expanding hole in the Milky Way suggests that corporations have not yet figured out how to be as dangerous as science-fiction mechanical superintelligences are alleged to be in their quest to maximize paperclips.

If we don't think that AI can be safely controlled, why do we think that corporations can be? Likewise, if we think that they can, why not the converse? Which fail-safes are effective for one, but not the other?
I do find it sad that we don't yet have a more efficient means of capturing the output of a nuclear reactor than heating liquid to power a turbine. Seems like there should be a more direct (and more efficient) path from fission or fusion to electricity.
I also thought it was easy to read and had no strong qualms with the style.
In Google's case there are a lot of people in the pipeline that all need to respond before you get an answer. All your interviewers need to get their feedback in. Any internal or external referrals need to provide feedback. And once that's all together, it needs to be presented to a hiring committee (and there are more steps after this that can take time).

(Good) recruiters at Google strive to get their candidates answers as soon as possible, but the most they can do, at times, is hound the person that is holding up the process.
RDF: A New Slant
It was an opportunity for a Google feminist PR cycle, that started with the followup comment from another investor who congratulated Google on diversity, the statements from the people on the dais, and the ladyday promotion.

The trigger event is just the stone in the stone soup, the macguffin, the tiny impurity that the crystal nucleates on. The specifics of the event have no relevance.
And in 1913 we didn't have even basic nuclear technology. Just 3 decades is a long time for newly emerging technologies.

>We're far from emulating networks on the scale of the visual cortex

In 2009 (ish) computer vision was a joke that could recognize very few objects a small percent of the time. Based on only simple color and texture, and sometimes basic shapes.

A few years later and computers were excelling at computer vision recognizing a majority of objects. A year or two after that, and they started to beat humans on those tasks. We already have super-human visual cortexes. Who knows what will be possible in a decade.

We will probably never understand the inner workings of the brain. Not because it's complicated, just because reverse engineering microscopic systems is really hard (imagine trying to reverse engineer a modern CPU vs merely designing one.) Especially hard because we can't ethically dissect living humans and do the experiments we would need to do.

But that's no concern, AI advances on from first principles. AI researchers invent better and better algorithms every day, without having a clue what neuroscientists are up to.

>People fearing strong-AI are the ones not involved in the field,

That's just incorrect. A survey of AI researchers found they give about a third chance AI will turn out badly for humanity in the next century: http://www.nickbostrom.com/papers/survey.pdf

>We thus designed a brief questionnaire
and distributed it to four groups of experts in 2012/2013. The
median estimate of respondents was for a one in two chance that highlevel
machine intelligence will be developed around 2040-2050, rising
to a nine in ten chance by 2075. Experts expect that systems will move
on to superintelligence in less than 30 years thereafter. They estimate
the chance is about one in three that this development turns out to be
‘bad’ or ‘extremely bad’ for humanity.

>in combination with Moore's law ending

Computers can advanced a long time after Moore's law. Google just released a special neural network chip that is equivalent to 7 years worth Moore's law. 3d architectures can vastly increase the number of transistors. Better algorithms can make NN's that require many fewer transistors to do computations, or even do cheap analog computations.
Yeah - getting ghosted sucks in any context.

But when they ghost you even after an internal referral? From someone you worked with previously?

That's when you really have to wonder what is going through these people's heads.
> And Gradle is so much easier than the monster that is SBT.

Totally is, but I've had better luck using Maven than Gradle. Having multiple mutually compatible options is great.
Just a crazy idea, but what if instead of TV/radio commercials and billboards and internet popup ads, products advertised themselves in the places they are sold (e.g. the sign next to a restaurant, or the side of a shampoo bottle on a shelf in the store), to explain very briefly why they're better than the competition? Most of the time, people will come across it organically, and that's healthy and good. But if discoverability is needed too, they can advertise in appropriate places, like restaurant listings, etc.
Thanks for the feedback! I'll pass along to the O'Reilly team and see if there's anything they can do.
People like to feel righteous and superior. Whether they deserve to feel this way is an entirely different story.
What languages does it support for code and templates?
In many ways it is much easier for a tiny country to achieve what Estonia did (fast internet, teaching every kid to code, gov't services online, pay parking meters by mobile phone). When the central gov't is in charge of a country the size of an American city, there can be less red tape. Online voting in the US, for example, would require the agreement and cooperation of cities, counties, states, and the federal government.
How would most Norwegians look upon an American trying to learn their language and assimilate (at least on a professional and social level)?
Seems like there's not much in the way, at the moment, about attaching EBS volumes, or using your own custom AMI. For example, I want to mount an NFS share on the host to connect some container data volumes to directories inside. I've asked about this on the new forum https://forums.docker.com/c/docker-for-aws
Lettuce uses such a different programming style I never tried it out. If you are looking for a Java Redis client, please try out all three: Lettuce, Jedis and Jedipus and pick the one that fits your taste.

Because I'm not familiar with Lettuce, I'm just going to list my personal subjective design goals:

* Robust transient error handling and retries.

* Get out of the users way when sending a command and its arguments. The client should get the request data onto the wire as soon as possible. The client should not force the user to use any data structures for representing requests or responses.

* Efficient pipelining support. Every client re-uses a single ArrayDequeue to optionally hold pending responses; no other data structures are created per request. See this gist for pipelined bulk loading https://gist.github.com/jamespedwards42/d03482c4b3515f78d1db....

* Frequent point releases in-sync with the Redis unstable branch. For example the new TOUCH command was added and released a day after being pushed to github at antirez/redis:unstable.

* Redis Cluster focused. you can use just the client or pooled client executer, but the cluster executor is the real reason to use this library. The focus here is safety: partition handling and minimal locking only applied to migrating/unavailable slots. As well as performance (under the hood --> clientPools[slot].getClient). Also, things like load balancing requests across all of your nodes for a key/slot is nice :)

* Make the development experience more enjoyable by using Java 8, Gradle and Docker. Hopefully this will attract other developers to the project so that a healthy community can grow. Goal is to move to Java 9 on rc1 in November, and to the Gradle component model and Kotlin instead of Groovy whenever that is ready as well.

* Zero dependencies, none, nada.

* I don't think this one really matters, but it is a pet peeve of mine. Avoid auto boxing by deserializing primitive long's directly from the socket input stream buffer.
This is true -- the first goal declared is the default.
Upvoted you, but adding on: a competent Java developer can pick up Kotlin in, literally, three hours. The mappings to Java concepts are trivial, but the language's niceties quickly bear themselves out as you go.
> (node, sublime, google chrome, , python libs etc etc).

Lazy comma usage. Come on!
Who would buy Coca-Cola from a gas station?
rustc itself loads stuff as a shared library, in my understanding.
In the olden days, companies would typically say it would take 2-3 weeks to give you a response. This was because they needed buffer time between extending an offer to their first-choice candidates, waiting for them to accept or turn down, time for salary negotiations (before the offer is final), extending an offer to their second-choice - and so on.

Nowadays, I think it may be a breakdown of the hiring or communication process. If there is a recruiter (outside) involved, the recruiter will likely not get communications about the ongoing hiring process since they involve candidates that the outside recruiter does not handle. If it is an inside recruiter, the inside recruiter might not even get communications if there are other inside recruiters competing to fill a position (silos, darwinism, bonus pools).

It would be nice if the hiring software platforms automatically sent a workflow-based notification based on where you were in the pipeline (e.g. 'did not pass go, did not collect $200'). However, I think that transparency into hiring processes advantages the candidates over the hiring company. The hiring company's advantage is that it (usually) has the power and controls information asymmetrically. There are most likely exceptions for exceptional candidates (think Google/Facebook AI team candidates) in which they don't play the hiring game but are simply trying to smooth the process.

This is why having an internal advocate is essential for getting into a company's hiring pipeline and knowing where you are in that pipeline (did the pipeline break for you, were you discharged into an outflow pipe after the on-sites etc).

Hiring is optimized for the employer's yield of quality employees, not for the non-accepted ("rejected") employees. Even though there are legal issues involved with specific reasons for non-hiring (e.g. worst case - discrimination lawsuits), it still benefits the company to be cautiously turtle slow with even black/white binary responses (no, yes - you are hired).

Since some of the most egregious companies (e.g. Google) have some of the most talented software engineers, you can imagine it is more a function of the culture (e.g. false positives are bad - it is acceptable to have false negatives) than the software/communication platforms underlying the hiring process.
I think both can be right. Ng and LeCun are talking about the real near future. Bostrom always came across as a speculative SF + philosophy kind of guy. Are there any specific critiques of his (and Yudkowsky/MIRI, Musk, etc.) arguments? I think the two claims are plausible:

1. AGI is imminent: 50 years or 500 years or more from now. This is not too unlikely given that the brain is just an information processing system. Emulating it is likely to happen sometime in the future.

2. Such an AGI will be all powerful because it is not limited by human flaws. Trivial or not, we will have to program it with "thou shalt not kill" type values.
I assume so, I was just trying to say that I am ignorant about BSDs in general, and don't know what the status of any of it is personally.
Generally I don't watch the nightly network news. Experimentally I've tuned in. It lives in a parallel universe, very weakly connected to reality. One has to invest many hours in its fictional narrative to make any sense of it, much like you don't tune into episode 50 of a pop culture TV show and understand any of it. You're no better educated given one episode of the nightly news than you are when given one episode of "breaking bad".

In that way one isolated pop culture clickbait artifact from a year or decade ago is useless. I need a package of ten, maybe a hundred hours worth of content to make any sense of the pop culture references and the self references.

From the front page of Reuters right now, clickbait era journalism that makes no sense without extensive background:

Texas 'affluenza' mom has curfew eased

Fiat Chrysler to investigate crash that killed 'Star Trek' actor

Wall St. rally holds steady as Brexit chances weaken

Myanmar's Suu Kyi reiterates stance on not using term 'Rohingya'

VLMs rule, clickbait expands until the content is indistinguishable from noise, without extensive experience and training.
Japan is hardly "tiny".
All fluid modeling at least. I once worked for a company that built heat exchanger simulations. I spent limited time in Fortran but was able to successfully integrate some C++ and C# libraries. The language isn't bad at all.
I've really enjoyed browsing nomadlist.com- great work. Haven't had a reason to pay- I guess I'm really just looking for inspiration- but I realize it fits a lot of people's needs.
I did notice recently that in the signup page, you took away the options to list various details about yourself, such as career, etc, and instead just have username and then paywall. What drove this decision? Is it for building email lists, or does this process drive higher conversion- or something else?
Sounds like a pretty serious bug that would probably affect millions of people....

... thanks for reporting it.

(https://www.sqlite.org/malloc.html)

"No memory leaks. The application is responsible for destroying any objects it allocates."

"Robust against allocation failures. If a memory allocation ever fails (that is to say, if malloc() or realloc() ever return NULL) then SQLite will recover gracefully."
This is a pretty useless article. Here is the ruling:

http://www.supremecourt.gov/opinions/15pdf/14-1373_83i7.pdf
If it is, expect the Panama Canal to start work on the fourth set of locks, and perhaps finish before the Nicaragua Canal.
We're still a long way from "strong AI". We need a few more ideas at least as good as deep learning. But it's a finite problem - biological brains work, DNA is about 4GB, and we have enough compute power in most data centers.

Right now we have enough technology to do a big fraction of what people do at work. That's the big economic problem.

General-purpose robots still seem to be a ways off. The next challenge there is handling of arbitrary objects, the last task done by hand in Amazon warehouses. Despite 30 years of work on the bin-picking problem, robots still suck at this in unstructured situations. Stocking a supermarket shelf, for example. Once that's solved, all the jobs that involve picking up something and putting it somewhere else gradually go away.

Rodney Brooks' Baxter was supposed to do this, but apparently doesn't do the hard cases. Amazon sponsored a contest for this, but all they got was a better vacuum picker. Work continues. This is a good YC-type problem.
A smart contract is pure reason (i.e., logic); if one misunderstands a contract, then the error is one's own, not the contract's

Pure logic is enough? Doesn't logic tell us this isn't the case? Isn't the Ripoff Problem reducible to the Halting Problem?

EDIT: Thinking on this a bit more, I have to conclude: No. But it's orders of magnitude worse!
Yes to testing LinkedIn. Twitter could also work if your audience hangs out there (you may be surprised...). On Twitter and LinkedIn you're catching people as they're browsing, not actively looking for a solution, so you should promote educational content rather than the product/service itself.
> I've heard right-wing people say work hours should be an employee-employer agreement that shouldn't concern the government.

That sounds like more of a hardcore libertarian position, which doesn't really fit neatly into the left-right dichotomy in my opinion.
These companies can take all the time they want.

The problem is that they continually bait candidates with promised turnaround times that very seldom have anything to do with reality.
For better recall, try a work out four hours after learning something
This tutorial is awful.

You should read the manual, which is shorter than that page!

make is NOT:

alias:
commands

this will bite you when you least expect. Make is:

targetfile: inputfiles
commands to get targetfile to exist

and you can use things like

%.css_min: %.css
sass stuff

.PHONY: release
# above is needed otherwise you won't build if there is a release/ dir
release: release-min.css

release-min.css: (list *.css_min files, there are helpers for it)
cat *.css_min > release-min.css

anyway. you get the idea. work with files and why you need those files.
I've heard the Wonderlic test is often used instead, possibly for this reason.
It's not Japan. It's Estonia. Please don't comment without looking at the article first.
You don't actually need to calculate the derivative accurately. It's enough to sample several points near the current one and continue the search to the best of those.

The point here is that we are descending in a continuous and monotonic loss function. You don't need an accurate derivative or even an estimate of the derivative to do so, although it definitely helps a great deal.
Articles like these make me wonder if the long-term progression of the PC revolution will follow the sexual revolution of the 1960s.

The AIDS crisis of the 80s did everything it could to undermine the last few decades worth of free love. Not only was promiscuity tinged with risk, that risk alone (and the lgbt association) opened the door to conservative ridicule.

Fast forward to 2016 and sex is better and safer than ever: hookup apps give you the opportunity to connect with people without the prerequisite of an alcohol-soaked atmosphere. Condom quality is light years ahead of what it used to be. Truvada and low-cost antiretrovirals have chipped away at HIV stigma. STI test results are an app away.

If an apocalyptic hack resembling this article occurs, it could spur on a similar security revolution among businesses and consumers. Only when people realize how insecure they have made their own lives will there be any chance of saving them from themselves.
I tend not to do much with Javascript, but if you have a project that I can take a shot at converting, I'd be curious to see what trouble you're running into.

Windows is the only real challenge there, but with mingw, I can't imagine that it's a serious one.
It's absolutely legal. Like any other screening tool that has significantly differential impact by race, it's only legal when it is sufficiently demonstrably related to performance in the specific jobs for which it is used as a screening tool.

There is a popular myth that it is illegal because of a case where it was found to be illegal in the specific manner in which it was used.

https://en.m.wikipedia.org/wiki/Griggs_v._Duke_Power_Co.#
The unbearable virtue of cleaning
Totally hear you on the death by a thousand tiny cuts :(

GCS provides multi-part and resumable uploads (https://cloud.google.com/storage/docs/json_api/v1/how-tos/up...), though I agree that the docs make it hard to find given how deeply they are nested. We use resumable uploads in Firebase Storage (mobile GCS: firebase.google.com/docs/storage) to great effect, and routinely upload some pretty huge files with no problems.

Definitely hear you on autogenerated libs sucking: the gcloud-* libs are designed to address some of those issues. gcloud-golang is still under development (https://github.com/googlecloudplatform/gcloud-golang), but might be a good place to start.

GCP is working to address a number of permissions issues with Cloud IAM (https://cloud.google.com/iam), which will provide more fine grained control over resources. I believe Cloud PubSub already uses this model.

Firebase (which shares certain services with GCP) has free developer support (firebase.google.com/support), and as you can imagine, we're inundated with questions and have two teams working 24/7 to address them. Free developer support is a great thing for developers, but providing high quality support at Google scale is probably the hardest thing to do--people just don't scale the same way machines do.

That's why so many of us are active on social media/HN/etc., we want to talk directly to developers and get feedback so we can improve our products, but we typically aim for high quality feedback (like this, thank you :), where we can engage with savvy developers to solve their problems, or at least get actionable feedback to guide our roadmap (x is a bad experience, have you considered y and z which would save me n hours). Ideally, this feedback trickles down into all areas of the product, and even across products (when it comes to permissions, console changes, docs, etc.), though it can take some time to implement those changes.

(Disclosure: PM on Firebase, and work closely with Cloud)
I'm curious too! I don't know yet whether they'll pass that info to me, and then I don't know whether I would be able to pass on any further. I imagine at least some of the analytics are considered proprietary/competitive info. But we can see some public things like votes here, number of tweets, etc.
If anyone knows about a single climate or weather prediction model that is not in Fortran, I'd like to hear.
To be pedantic, the proper character to use is "×", not "x".
So you want to go into DevOps
I interviewed a coding bootcamp person in SF and found them to be quite competent and able to handle stuff at a level I've seen from engineers with 3-5 years of experience in the field, along with their CS degree. Other interviewers also had a positive experience with this person and we made an offer, but in the end they decided to take a competing offer...from Google.