skysight-inc/HackerNews huggingface dataset:
Most of the tweets are about implementing specific famous algorithms (bubble sort) or about language/library trivia (reading from input streams in Java) or esoteric computer science theorems (np compete). All of these are the exact opposite of whiteboard coding interviews.

The whole point of whiteboard coding is that candidates are given a small problem/spec, and to solve it using any language/psuedocode/algorithm they want. The fact that you can ace a whiteboard coding interview without knowing anything about input streams, or bubble sort, or np-complete, is the entire rationale behind this interview style. The fact that whiteboard coding interviews are so precisely objective and formulaic makes them so much less prone to bias, as compared to bullshit interviews where you're asked to reminisce on past projects and your greatest weaknesses. Almost every tweet shown in the article only succeeds in validating the whiteboard coding interview.
So you have never been on the road, and avoided a car crash when someone else screwed up?
MailShrimp
RL is special in the sense that your actions do not produce immediate feedback, and feedback are only available after a period of time.

E.g. You ate an apple, you opened the door, you arrived at office, and then had food poisoning.
docs updated at http://johnkerl.org/miller-releases/miller-5.0.0/doc/build.h...

and, https://github.com/johnkerl/miller/issues/131
First the fall of human civilization has to be a real threat per the TOS so not sure they'll care.

Second, I know the lawyer and yes he had fun.
> No, my point is that none of these disciplines have been remotely subsumed by their "rigorous" counterparts, because their subject matter is fundamentally different. All of these "rigorous" fields are, of course, fed by philosophy -- but they are not in a position to turn around and solve philosophy.

No they can't answer many of the questions some philosophers have asked, but they can and have shown that many of those questions were poorly defined. For instance, biology and biochemistry have completely supplanted the philosophical debate surrounding vitalism.

Slowly but surely, I also predict neuroscience will erode many of the foundations surrounding dualism. Which isn't to say that those fields will be free of philosophical questions at some point, because that's just not how knowledge works, I'm merely saying that many of our current philosophical questions will either be answered or will be shown to be poor questions.
General AI Won't Want You to Fix Its Code – Computerphile
Does anyone know enough to lend some context here? I gather this works similarly to ConvNetJS, or solves some of the same problems. Does it go further, or work in a different way, or what?
yooge crowds, not huge.

to all downvoters, just in case you missed, this was a parody on Trump. and pretty good one:)
Part 2: https://www.youtube.com/watch?v=3TYT1QfdfsM
JailBlimp
> And if he took a Lyft, a private limo, or drove himself, that would be even worse publicity. Right now no matter what he does he'll get people sniping at him, just like on this board. It's a herd mentality where you pick on perceived weakness, and it's always ugly.

I'm not saying he shouldn't take Ubers. I'm responding to the comment "he is a guy in his private life who has been blindsided". He should have every expectation that any driver he gets might ask him about the business, even harshly. It's completely fair game. It's his job to deal with it without losing his cool.

> Does every single McDonald's worker in the world know what the CEO looks like?

The cult of personality around Kalanick is huge, and he is making daily decisions in a volatile industry that directly affect the lives of tens if not hundreds of thousands of drivers. They are very likely to be following his every move in the news. In any case it doesn't matter how many drivers recognize him, all I'm saying is that he should have no expectation of privacy if he takes an Uber. Drivers are very likely to recognize him and should have every right to ask him tough questions.
i very much like the background artistically, and it's unobtrusive for me, but it seems that on different monitors / browsers it's less so. in any case, the background is now white. thanks for the feedback!
I stumbled across this site from one of those "/g/ acts like HN" threads a few months ago and it's quite funny. I think my favorite summaries so far are:

The Muskonauts figured out why their shit exploded. Hackernews, literally all of whom are actual rocket scientists, wonders if unit tests could have helped.

Russia addresses their worst nuclear contamination problem by putting a shed on it. Hackernews trades photos of the devastation and bitches about people getting paid money to work on the shed.

An astronaut has passed away. He retired from NASA in 1976, since which time humanity has been phoning it in with this whole space-travel scene. Half of Hackernews recognizes this as the massive failure it is; the other half seizes the opportunity to virtue-signal about all the other problems nobody's fixing.
One more thing about Password Store: You can integrated it with a NFC-equipped Yubikey on Android so you don't just have a GPG key floating around. It took a little while to set up, as I was a Yubikey newbie at the time, but it works really well for me now.
Disclosure: I'm one of the co-authors of the QRNN paper (James Bradbury, Stephen Merity, Caiming Xiong, Richard Socher) produced by Salesforce Research.

There are many interesting advances that Deep Voice paper and implementation make but the part I'm excited by (and which might be transferable to other tasks that use RNNs) is showing that QRNNs are indeed generalizable to speech too - in this case in place of WaveNet.

"WaveNet uses transposed convolutions for upsampling and conditioning. We find that our models perform better, train faster, and require fewer parameters if we instead first encode the inputs with a stack of bidirectional quasi-RNN (QRNN) layers (Bradbury et al., 2016) and then perform upsampling by repetition to the desired frequency."

QRNNs are a variant of recurrent neural networks. They're up to 16 times faster than even Nvidia's highly optimized cuDNN LSTM implementation and give comparable or better accuracy in many tasks. This is the first time that it has been tried in speech - to see them note the advantages hold across the board (better, faster, smaller) is brilliant!

If you're interested in technical details, our blog post[1] provides a broader overview and our paper is available for deeper detail[2].

[1]: https://metamind.io/research/new-neural-network-building-blo...

[2]: https://arxiv.org/abs/1611.01576
All this so that I can not have one of those unsightly antennas near my tv? Sign me up! /s

No, really, this is too much money. And with data caps, I don't really think I'd get my $35 out of it.

Besides, who know what Ajit Pai is going to let Comcast do? Won't be long and I'll have choices like:

Basic internet - for reading email.

Basic Plus Internet - Basic internet + Amazon shopping (but no streaming)

Internet + streaming - Basic Plus Internet + Comcasts own streaming service.

Internet Premium - Internet + streaming + Netflix, Amazon and YouTube streaming.

etc...
You could just admit you didn't read it that carefully and move on.

This article appears here because of a larger political context, which is explicitly mentioned in the article. My comment is relevant for this reason. I'm sorry you disagree. It would be great if you could respond to what I said instead of picking a nit about what percentage of the article would have to be related to my comment for it to be relevant to you.
The point of having something like PUT (that is known to be imdepotent) is that it can be retried by any of the layers in the stack, instead of having a full roundtrip back to the client on every retry.

And it's not always safe to retry POSTs. If POST is an insert, for example, retrying it would produce two inserts. And this can have interesting consequences when processing responses. Suppose that you have sent a POST request, but before you could read the response, connection dropped. You didn't get a chance to read the status code, so you don't know if your insert succeeded or not. If it didn't, you want to retry - but you'll need to do a GET first to check the current state of affairs. OTOH, if you're doing a PUT, you can just retry immediately without re-checking.
I think you're onto something with domain-oriented real-time feeds. Finance is one huge cake, perhaps not the only one. Sports, politics come to mind.
hmmm I would say philosophy "clarifies" where mathematics comes from.
She quit her IBM job to found a diaper company
> "Kalanick's opinions and behaviour are obviously of interest to the public right now.

Not really. Uber's actions are, certainly, but the opinions and actions of the CEO in his personal life are only of interest here because technology executives are the celebrities of Hacker News readers.
make it a non-profit. It's in the public interest.

No, a walled garden webapp is not a public utility.
I found DMOZ pretty well curated and responsive to requests... 15 years ago. If you tried to submit something recently though then, yeah, you were submitting to a zombie site.

Wikipedia, as it happens, curated some data illustrating the growth prior to ~2004-05 followed by complete stagnation; see the graph in this section: https://en.wikipedia.org/wiki/DMOZ#History
That's exactly why I gave in and paid for basic cable. Which ends up costing $17.76 ($10 HD fee, $5 broadcast TV fee, $2.76 taxes and fees). For access to free content.

I also bought a good indoor broadcast TV antenna. A winegard one, I think. And it normally works great, but it's only 90% reliable.

I wouldn't pay the extra $17.24 for nothing, but I'd like to watch some sports too.
> 2. allow the apps to be used without a login - with the default view showing 'what is on now'

Twitter generally needs to get a lot better at predicting what you'll be interested in (think Pandora.) Just based on the IP they should be able to tell a lot. Tweets that have been recently favorited, retweeted etc. in just your area would make a very decent default view (band coming to town! metro closure! the mayor is a jerk! etc.). Once you create an account they should also be able to predict a lot based on your activity. Oh, and please give us a Hide Tweet button. There are talkative people I'd still like to follow - but maybe a little less.
The specifics of how this will work are not totally clear to me, but web assembly will have a text format that will be human readable and editable according to:

[0] http://webassembly.org/

[1] http://webassembly.org/docs/faq/#will-webassembly-support-vi...
But we don't know that. All they've told us are the OTA channels.
We shouldn't examine a scenario, hold all but one variable constant, and see how things change? Why not?
A profound apology
This article is largely bollocks.

1) Almost every gripe in it refers to bad implementations, not bad specs.

2) It doesn't even mention HATEOAS. I'm no fan, but usually arguments about whether your API is REST or not revolve around how/whether you've done HATEOAS.

3) The rest of it is pulp tech writing that sounds like it was vomited out to meet some kind of publishing deadline.

Case in point:

> Consider, for example, when we might use the 200 OK response code. Should we use it to indicate the successful update of a record, or should we use 201 Created?

Here's a clue - read the spec! (SPOILER ALERT: the word "Created" is the giveaway). To quote:

200 OK

The request has succeeded. The information returned with the response is dependent on the method used in the request, for example:
<snip>

201 Created

The request has been fulfilled and resulted in a new resource being created.
AVG PC TuneUp 16.74.2.60831 Crack 2017 with Serial Key Free Download
> PHP doesn't have that for example.

Bare PHP, sure, but pick basically any framework that any modern PHP-based web app is built on and then it does, no?
I think the parent was joking.

Though there are people on HN who can do that, given some development time, like me.
I actually really enjoy whiteboarding interviews if they're closer to what you'd use a whiteboard on the job for: discussing some problem, pros and cons, designing a solution, even details of an algorithm (as opposed to implementation).
1) remove the 140 character limit. It was not a problem when you wrote it, and it definitely was not a problem today.
2) two factor phone verification should be removed. It makes people want to leave. Allow it to be turned on as an option, but don't force it in your users.
3) allow users to user your service without having an account.
4) increase the number of data analytic tools available for public use, tools that can explore relationships between social networks and postings
5) remove the whole ghost-tweet feature. No one hates it more when a site says Yes this message was posted, and then you look back and it really wasnt. It frustrates users, it also will make them leave, by the millions.
6) stop censoring speech and removing accounts for trivial behavior through speech. If anything replace it with a user voting feature so that posts can be flagged for different types of bad content and reported. The whole censoring option needs to be toned down about 1000%. No one will use your service if you keep doing this. Why should they? If you don't allow them to publish, one of the other 50 twitter clones will.
The mobile version seemed like it would be fun if it was your first experience with Majesty. It doesn't hold a candle to the original, though. Fewer heroes, monsters, missions, and worst of all, dramatically simpler and less character-ful AI, with few apparent behavioral differences between classes.

Also the art was entirely redone in the generic cartoony style of every other mobile RTS. I suppose it's more approachable than the original's 2000-era pixeliness, but it didn't seem like an improvement to me.

It's still better than 99% of all mobile games, but that's not saying much. The original is on Steam for $10 including the expansion and various bugfixes; I played it through again last year and I think it still holds up wonderfully. http://store.steampowered.com/app/25990/
So much so that maybe ICANN should just work on something like it as a public utility?

Look at OStatus for a model for this:

https://www.w3.org/community/ostatus/

https://en.wikipedia.org/wiki/OStatus

Note that there hasn't been a lot of traction here, although there are a few interesting implementations with active userbases.
According to the blog [1], the DVR lasts 9 months. Which is much better than the competitors, but not "forever".

1. https://youtube.googleblog.com/2017/02/finally-live-tv-made-... "we’ll store each of your recordings for nine months."
There's a different standard for public figures.

A relative of mine was a chief of a fire department. During a nasty contract battle, he had people picketing his home -- a miserable experience for his family at the time.

But... he was a public figure and the protestors were on a public sidewalk.

When you're a public figure that carefully nurtures a bad-boy, asshole image and attitude of privacy bordering on contempt, you shouldn't expect kid gloves.
None of these things are true about MS Office (native - not online 365) right now, which was the specific subject this sub-thread.
Fwiw, it's heavily entrenched at every level and in every vertical. The incumbent competition has often had 50+ years to stake out their claim and build relationships.
I think the first comment/reply to the post hits the nail on the head, by Florian Klein[0]:

> Awesome! You replaced REST with REST. How revolutionary:

> Instead of transferring application state through the wire via one of its representations,
> you know transfer its state through the wire via one of its representations.

> Do I need to go any further?
> I think so, because to me your confusion comes mainly from the vocabulary you seem to misinterpret. You didn't even talk about hypermedia or links! That's kinda strange in an article about REST.

> Even tho I agree this vocabulary can be confusing, you should not throw the stone on the wrong subject (REST).
> Your problem is HTTP, right?

> Rest is not tied to http at all, and your point about making response bodies self contained is an honorable idea, but it doesn't change anything to your application being RESTful or not.

I work building, debugging, deploying and integrating JSON-formatted RESTish web API's every day. I find purist API's to be the most painful to use, and I find people who take the this-is-pretty-much-RPC-over-HTTP approach to be the second most painful unless it's perfectly built for my use-case.

There is a perfect middle-ground for most API implementations and really it comes down to the architects and software engineers implementing the API being able to think like API consumers and thinking of most use cases for their API's up front, then having a good level of "80% of people will use it this way, so we'll try and cater to the masses but support the other 20% like this".

There are definitely the marketing types who sell REST as the be-all-end-all solution to APIs, and all the other bells and whistles that go along with it. That isn't unique to REST.

I'm not on a mission to appease 100% of all use-cases for an API or integration. Such a solution will never exist and people trying to make out like there must be some sort of "holy grail" of API definition and design out there and %insert_current_fad% is wrong! No. We're doing our best, and today's API's with their API Test Consoles and their interactive walk-through's for people new to the API are a hell of a lot better than what we had before.

[0] http://disq.us/p/103w6z6
https://wefunder.com

Note: weirdly high number of coffee and alcohol brands.
An Idle Brain Is the Devil's Workshop, please keep me busy
Why do so many Google employees appear to plug their stuff nearly every day?
Good or bad or other, Google seems to be the only company that engages in this sort of cheerleading on HN. Does anyone else think this is a strange state of affairs?

If it's a new service announcement, there will be an army of people to answer questions and solve support problems. If it's a story about a competitor, there will be an army of people prodding you to try Google instead.

Even if this isn't an organized part of their media strategy it still smells a bit off, no?
> Neuroscience studies various structures and mechanisms of nervous system and brain. Even when they seemingly discuss 'consciousness', they tend to simply mean 'awareness'.

You should give neuroscientists more credit! Some of them are aware of the philosophical problems surrounding subjectivity, and have tried to tackle them [1]. That's one of my favoured scientific theories on the source of subjectivity.

I can also sympathize with the disdain with whic some neuroscientists view some philosophers of mind. They've debated some completely ridiculous theories of mind in order to rationalize human importance. These consciousness debates are following the arc of vitalism, which the science of biology eventually simply replaced, and I expect these neuroscientists see it as a waste of time for similar reasons.

[1] http://journal.frontiersin.org/article/10.3389/fpsyg.2015.00...
Twitter at the very least should adopt a standard and work with standardization bodies to improve the ability to federate and "self-host" your own Twitter on your own infrastructure.
In that case we're using the wrong word. Tourists go on "tours", not "missions".
Twitter is not a community. It's a platform. There's a difference.
Any man who must say "I am the King", is no true King at all.
Yeah, that was the original pitch for AWS. Engineering presentations since the initial launch have included "yeah... not quite" admissions though.
That feels like a vestige of Twitter's origins as a heavily SMS focused service. Even if that is true, though, odd to have such a high friction element to the registration flow for what is now a niche use case.
Here's one guy writing about VA C++ of that time:

http://www.tarma.com/articles/1996sep.htm

"Let’s not beat around the bush: VisualAge for C++ for Windows is a disaster as far as I am concerned. It is by far the most anti-productive environment I ever came across, C++ compilers or otherwise."

"The wizard-like approach for project configuration takes you through a number of tabbed dialog pages à la OS/2 (with spiral binders and all that), and they simply look gross on the Windows platforms. What’s worse, elementary options such as a Browse button to navigate to a project directory are missing."

"A static library is not among the options as I found during one of my tests, but for the ones that are, you sometimes wish you’d never started in the first place."

Etc. I also remember it looked visually weird. And that it didn't do what I expected an IDE to do. He describes that and also some strange manual steps.

Another guy, later version:

http://www.edm2.com/index.php/VisualAge_C%2B%2B_4.0_Review

"Installing VAC4 can range from a trouble free walk in the park to something akin to being in the first wave landing on Omaha beach. I have installed the OS/2 and NT versions on multiple machines with varying, mostly good, results. However there are some really nasty horror stories in the news groups about installs going awry. In my experience installation problems seem to revolve around four issues:

VAC4 is very picky about hardware. It will complain or not run on a machine that is seemly running everything else just fine. I've run into this more with OS/2 than with Windows."

"Once you get VAC installed there is one fix pack for version 4 and two fix packs for version 3.6 that you need to install which take care of a number of bugs. The fix pack installation also uses Feature Install. Did I mention that Feature Install really stinks?"

I'm sure I haven't had "fix packs."
New Google Patents front end breaks Zotero import feature
I think what JPMorgan fails to realise is that their entire business will be subject to automation. In a way they are signing their own death warrant. Obviously they will reap the benefits of AI while it's in it's infancy, but it won't take a quantum leap to realise that most of their business can be replaced by software eventually.
Does this include adding 23 chars for a link, and possibly also for images (which I think used to count as extra but no longer do)?
Meh .. I think Paxos is easier than raft. A lot of Raft's complexity is in leader election, getting rid of old leaders, etc. Sad that I have failed Google's whiteboard interview soooo many times that I don't bother returning messages from their recruiters.
Assuming it's the same as the Android version, it's superficially polished and internally hollow compared to the original. I posted more here: https://news.ycombinator.com/item?id=13760412
I'm not sure I see the advantages. It's a lot more verbose, based on the few examples I'm seeing there, and strongly reminds me of SOAP, XML Schema, and the rest of that over-complicated stack.

I suppose some amount of complication would be fine if the benefits were clear, but I feel like I could implement a client and a server for the less-verbose API that you start with, in the amount of time it would take to implement a server alone with all those bells and whistles. And I can't think of any scenario where they would actually add value.

I think the reason why RESTful APIs with very simple JSON payloads became so popular is because they get the job done with so little effort and so few abstract concepts to grok. This feels like a step backwards in that respect.
One of the best vuln write-ups I've read in a while, in that it steps you through how the initial entrypoint was found, and the steps needed to turn that into a dangerous exploit.

I think what really makes this writeup worth the read is the insight it shows into the thought process of identifying an interesting bug and weaponizing it. Thanks Frans!