skysight-inc/HackerNews huggingface dataset:
In the U.S. at least we often refer informally to a metropolitan area as a city. For example, I work in an office that isn't in the city limits, but is instead outside the city by its airport (one of the busiest in the country). We still say we're in the city, even though we're about 20 miles away (though we do have the city in our mailing address, even though we're in the city limits of a suburb).
Microsoft is like, "It's totally a good idea to build an AI sculpture of today's 18-24 year old American chatting behaviors"...
[nevermind]
I would say that what's most harmful is using code coverage as the primary measure of quality of your tests. It's that mindset that puts coders in a mode where they write tests which upon failure mean nothing significant (unless it finds a runtime error). It's a type of fallacy. Instead of considering if your tests verify your real-world requirements, you feel like your job is done because you have reached 100% line coverage.

It's like following someone's car and congratulating the driver that he drove correctly, without considering if he reached the correct destination.
Cruise Automation (YC W14) is hiring engineers to build driverless vehicles
If aliens are indeed to be found, this will readily become number one important event in human history.
yeah OK that makes sense.

So what about:

- Humans are an ordinary species

- Humans live in an ordinary galaxy

Does that change our relative height?
This sort of comment could be based on real knowledge, but it's hard to tell because you just gave us a conclusion rather than showing us how you came to it. A better comment would add information: give an example or two, tell a story, or say what's behind your thinking somehow.
Maybe more encouragement of caching where NPM downloads into places where it can be checked into source control. Then you can have the beginner friendliness of NPM, but you are only relying on it being up when you want to add or update a package.

Pretty much the only thing needed to accomplish this is to discourage the use of the global flag, and a few strong notes in the documentation and tutorials to check in your node_modules folder that remind people that if you don't check it in, you have established a build time dependency on NPM being up/correct.

edit: corrected spelling
I'd consider it a serious code smell for my codebase to be carrying around my personal attempt (or my team's attempt) at at half of the Python standard library. When it looks like we're heading in that direction, let's just use Python!

Sure, if it's really just arithmetic on lists, I won't be happy about it, but I'll write it. I've yet to meet a standard library which is wonderfully complete except for that one thing. If the abstractions of the environment I'm working in are that poor, there's going to be a thousand other little "trivial" things that I'm now responsible for maintaining, and some of them will turn out to be less trivial than imagined.

For example, it is "trivial" to write linked lists in C, but tracking down the one-character typo that causes them to nondeterministically explode is IMO a distraction from the project, not a valid part of it.

And what about the next project in that language? Wouldn't it be nice to factor out all that stuff and bring it with me? Well, now I am using a community standard library, but it's the community of "just me." Why not take one with some internet recommendations and an active Github?

My employer fortunately runs its own package mirrors, though, so we don't run the risk of packages just disappearing on someone else's whim.

I suppose our difference in values is that I consider each line of in-house code as much of a liability as you consider each line of other people's code.

My reaction to the article is very simple:

>What concerns me here is that so many packages took on a dependency for a simple left padding string function, rather than taking 2 minutes to write such a basic function themselves.

"So many people" writing a basic function themselves is an exactly wrong outcome IMO.
A light but featureful alternative to omz is also the grml zsh configuration [0]. I've been using it since 2011 or so and I've probably touched my .zshrc once or twice. If you fancy some colors you can also add some syntax highlighting [1]. Or just use fish which is great for interactive use!

[0]: https://github.com/grml/grml-etc-core/tree/master/etc/zsh

[1]: https://github.com/zsh-users/zsh-syntax-highlighting
Ad Spend Calculator for Healthy Business
Setting is here: http://imgur.com/qwpukly
You win if the photon is measured by the win-detector, as depicted here: http://imgur.com/STjajMp (it can light a green led, make sound or, I don't know, launch confetti). People pay money, as it was a bet.
Follow the link from here to get free access to this article: http://www.businessinsider.com/tony-fadell-on-alphabet-2016-...
Extortion, hacking claims sparked FBI investigation of HubSpot
So you're saying people think it's a trump card, but actually it's a Trump card?
you should know, i'm trademarking the number 0.0.3 so i ask you politely to change it... LOL
Like threats on your well-being and earnings is not "being a dick".

None of us should be subject to such behavior no matter how many trademarks, patents, consumers or money they have.

They should name their package kik/dick-kik so it "won't be confused" with other packages. Ever.
What fucking programming language should I use?
Because it's beyond your ability to prevent, and your inevitable failure has terrible side effects.

Are you seriously tell me that facebooks real name policy has made cyberbullying less hurtful?
Roofing Contractor Warranty – All Roofing Solutions
But who monitors the status of statuspage.io?
It seemed fine by the time I saw it, but we took out the magic 17. The weirdest and most surprising of the tricks PG came up with for improving titles: https://news.ycombinator.com/newsguidelines.html.
...and Redshift. I love what Amazon provide, but it gets expensive.
This does need a warning, but PDF isn't the reason.
It all depends on who has the money and therefore the power. When the newcomers are wealthier and inclined to view the residents as undesirables, you get this sort of thing.

It goes the other way, too. In Amarillo, where I grew up, some neighborhoods had an influx of Vietnamese working in the meat packing industry; near where I live now, there's a large community of Mexican immigrants doing chicken processing. In both cases, take a wild guess who the police have problems with.
The conflict between the article title and the domain name is delicious.
I'm pretty sure secret societies and private groups will start forming as a result of people being pushed out of their right to speak openly about what they believe for fear it will offend others and ruin their careers.

It's probably already happening.
Greenplum is based on postgres 8.2, with the featureset you'd expect from pg 8.2 - basically none of the additions after 2006 have merged to GP.
I just used crypto as a random example. I could have said "this is why I write my own input sanitation library" or "HTTP" library.

My point is OSS is a collaborative effort by often times anonymous contributors. Therefore there will always be a risk of bugs or back doors - regardless of the distribution mechanism.

In my opinion any criticism against micro packages is equally valid against large packages. There's no guarantee that a pull request would receive any more scrutiny than a external dependency. I mean look at heart bleed. Surely this doesn't mean that OSS is broken, but rather stricter security protocols should be in place. My 2 cents.
Hmm that's unfortunate. How do I become un-dead?!
Computer programmer: one of the largest gender wage gaps among all professions
> One problem with reactive programming (and also with promises), is that you are essentially using monadic composition in an imperative language. Because of the lack of special support for monads that you have in a language like Haskell, you have.to.chain.flow.control.methods. As a result of this, you lose access to the standard flow control the imperative language provides you, and you also generally end up with mangled stack traces. Now I know that rxjs5 is working on the stack trace problem through the usage of a recursive scheduler, but I'm not sure how this works on the Java side of things.

Your point is kind of validated by C#'s introduction of async/await at the language level. If Rx extensions for .NET would have lived up to their promise (and those are much, much more mature that the poor man's imitation that is RxJava), there would have been no need to introduce a completely unrelated mechanism for doing async work (and mandate its usage in the Universal Windows Platform).
Agreed. We gave up on it and created a local beefy server that we shared for docker testing, but then we have port collisions and the other problems that come along with sharing.

Native is better and I'm very excited for this.
I wrote this article out of wondering how to organize code that follows the Elm architecture. I wanted to divide the code for parts of a page (call them components, sections, blocks, etc., I'll call them features from here on out) into their own directories. I wanted each feature to be independent of the others, but find a way for them to communicate information with each other. Finally, I wanted to see if I could group some of these features together to assemble larger features, while still keeping the same pattern of inter-feature communication.
If You Drive the Right Speed, This Musical Highway Will Play You a Song
Comments moved to https://news.ycombinator.com/item?id=11352307.
Intelligence is not gender related, although "intelligence" is hard to define and measure. Likewise, for authorship skills. Journal articles and citations are not, necessarily, the ideal measure for creative insight in science and mathematics.

For male authors to be so dominate suggests that there are other, probably social, factors at play which limit the success of female computer scientists. My female scientist friends report that misogyny is a common character trait of their male colleagues. Your response might be taken as supporting evidence.

In fact, sex differences in intelligence is controversial; Wikipedia has a nice summary of the various results, conclusions, and refutations: https://en.wikipedia.org/wiki/Sex_differences_in_intelligenc.... The complexity of measuring and testing intelligence is significant and many (most? all?) of the studies that have been done are of questionable validity.
Many are meta studies that confuse correlation with causality. (For amusement: https://xkcd.com/552/.)

Anecdotally, I have known many brilliant female scientists who have abandoned their field simply because of the behavior of male "colleagues" protecting their turf.
>You ask of evidence in a thread about a man being killed by police emptying multiple magazines into and the area around him.

This is a question of accuracy and situation awareness, not of intention when shooting.

>That doesn't even sound like shoot-to-kill that sounds like they were afraid to death.

My question was directly related to the comment made about shooting to kill, not about when to shoot.

>There's plenty of more stories of where that one came from. Were you unaware of that?

Stories about shooting when you shouldn't, not about shooting to kill.

>A policy of shoot-to-kill tells the populace

No, the policy of shooting too soon, without assessing the situation, is the cause of the problem. There is a distinction between when to shoot and how one shoots once they have made the decision. My question was focused on a comment made about the latter.

>I take issue to the police being justified in using lethal force as a first resort.

And I agree they are too quick to shoot. But my question was directed to a comment made about how they shoot once they shoot, now about when they shoot.

Where is the evidence (or argument) that shooting to kill is, and I paraphrase, something that is incredibly stupid? Arguments supporting knowing when to shoot, knowing what is around the target you are shooting, knowing how to shoot such that you hit the target do not answer this question.
People have made this argument against FICO, for what it's worth. (FICO is likely the most consequential AI employed in the United States outside of the Googleplex. It is not called AI because AI as a field demotes anything that ships into mathematics or engineering.)

FICO operates off of credit reports, which have no explicit way to encode race in them. It is fundamentally a clustering algorithm. It is very good at clustering.

(There's a good counterargument to be made, which is that FICO actually clusters people based off observable behavior and the system which FICO supplements/replaces -- human underwriters -- cluster people based on "Tom is an upstanding Christian who goes to my church; of course he is good for the money.")
Pony Foo Weekly – Issue #3
True many people aren't comfortable sharing things immediately, but much psychology on reciprocation tells us that your sharing things about yourself opens them up, moderated by their personality, mood, the context, and a bunch of more variables. Sharing about yourself (not too much, and listening and being genuinely interested in finding out about them without the interviewing barrage), is a great way to develop a rapport.
Sorry - for some reason Trello wouldn't let us create a Board the first time. We're looking into why it happened.
Who would bet on someone's death? This doesn't seem plausible.
Traditionally, yes. But the PE guys now have big enough funds that they need to broaden their thinking about what kinds of companies might be appropriate for their own special kind of love.

Also, the way PE finances are set up, the general partners collect big fees when deals are done, regardless of the outcome. The limited partners bear most of the risk of deals that don't work out. Since general partners call the shots, a 100% chance of getting deal fees plus a 20% chance of having the deal work out creates a deal with 120% upside. i'm oversimplifying slightly, but the key point is: Such deals get done.
apologies, you are absolutely right. Has been a very long day :)
Video Screencasts for Learn Enough Git to Be Dangerous
It's telling that only the immature JS ecosystem thinks this is a good idea.
Scheduling Systems Associate
> Throughout this whole thread are examples where these one or two line "modules" have poor runtime performance, miss key cases in the one single thing they claim to do, and in the very worst cases, those small "modules" themselves are depending on many more "modules".

Where? I've only seen the exact opposite: folk who don't believe in package management write their own naive 'reinvent the wheel functions' with those issues. Nobody I can see is quoting actual npm modules.
Whites are murdered in broad daylight too. Police accountability is, in general, lacking.
I mean, if that's an infinite chain, where does that weighted calculation stop? That's such a moral dilemma.
What's likely happening is someone's vouching for your comments. I did that for your other one.

You should rapidly become considered a normal user, but I'm told emailing HN is what you do if you continue to be auto marked dead.
How all those new virtual reality roller coasters work
Callback hell is a "loss of composition" problem. Most languages, including JavaScript, have things called expressions. Expressions rely on functions returning their output. They become useless when functions give their output through a callback passed as their input: they don't compose with that frankenstein.

Node style callbacks are a prime example of how in the quest for "simplicity" and hate for abstractions its easy to build a monster / frankenstein like caolan's async. Node callbacks were a self-contradicting philosophy: it abandoned all thats already in the language in the quest to avoid an abstraction that was not already in the language :)
still just VMs?
> using someone else's defaults.

Aren't you already doing that when you load up a vanilla zsh? Its just that that "somebody else" was the guy that wrote the tool. In either case, you still will want to tweak it to get exactly what you want.

However, in one of the cases, the thing you start out with is 0 features, and an extra week of work doing the same thing that thousands of people have done exactly the same before you. Only after that do you get to making it really "custom"
Ya what does the zero chill even mean? I might be too old to understand this.
Some Thoughts on Microdependencies, NPM, and Node
In a way, there is. The Challenger disaster drastically changed how information is propagated up and down during a launch, including how small an issue can be before a launch is scrubbed. I guarantee you there is no launch where Challenger doesn't run through the mind of every person sitting over the launch in Houston.
This is one of the faultier parts of having to answer to share holders. Apple is finding it more difficult to justify having their own entire supply chain rather than relying on other companies (i.e. Intel, IBM, Samsung, etc...)

If they didn't make that horrible mistake of their recent multi-billion dollar purchases, they'd have extra billion atleast towards a fab plant.

I'm laughing at Apple right now. Idiots. You Apple board... are stupid.
Mac OS X turns 15
Website of security certification provider spreading ransomware
As usual in these pay gap discussions, I see nothing about aptitude or capability. Until all factors are addressed, it's a non issue with me.
I'm amazed at how big the batch is. It seems like there are some clear front-runners, but the batch itself seems quite deep.

Disclaimer: Haven't payed a lot of attention to YC batches since '13.
I think there are people who are aware of the problem, but that problem is people reinventing the wheel a thousand times, and relying on copypasta and needless work rather than package management.
I would argue that this article posits a new, compelling filter.

If most species are large, and from small planets, they will have much stricter resource constraints than we did.

As a result, they are unlikely to have industrialized the way we did, as it would have depleted their resources too quickly. As a result, they are unlikely to be a silicon-age species.

Drawing from the author's biological/size argument, they're likely to have longer lifespans than we do, and considerably fewer births.

Given their resource constraints, and longer lifespans, they are likely to have strong communal systems of resource allocation, and are unlikely to have moved towards Capitalism.

Given their longer lifespans, they are probably more risk averse than our own species -- as willingness for an animal to die is strongly related to size and lifespan. This suggests they may be less war-faring than ourselves, and thus less likely to have nations.

Given their closer relationship with nature, due to their resource constraints, they're likely to have developed a Pagan system of thought, rather than a monotheistic theology.

As a result, they are unlikely to be motivated towards large infrastructural, imperial or technological projects as a result of: profit motive, national motive, or religious motive.

I'd argue then, that it is unlikely they have produced a civilization of significance.

--

Long story short; local alien species are likely to be tribal, communist, non-technological, and environmentalist.

If through some strange force a species of this kind managed to become technologically advanced, they would likely look down on a species such as our own as a sort of vermin, because of our numbers, hunger and short lives.
It sounds like a hard life out there in Bernal Heights.
Everyone is blowing the "micropackages are the problem" completely out of proportion. The real problem with the left-pad fiasco is that someone was able to revoke a package other people depended on. Packages should be immutable.
Ask HN: Contacted by Google Recruiter
Hi, I was contacted by a Technical Recruiter with Google and it seems they work with Nelson Staffing. They wanted to talk to me the next day, and despite having given them times for next couple of days and 1 follow up email, they haven't responded at all. Should I be worried that they dropped the ball and my application will be forgotten?
"Larger coherent efforts like lodash" already exist and are used by many people on many projects. Perhaps Node's real problem is that it allows developers to structure each project in exactly the way that they feel is best for that project, rather than enforcing a "Java way" etc. A greater variety of techniques naturally yields more techniques that bother any particular developer's sensibilities. Those who don't like the "Java way", for instance, are likely to simply avoid Java rather than tweeting, "OMG I just realized that you can write Java the Java way!"

It's a matter of taste, and Node accommodates various tastes.
I misunderstood you, and also wasn't very clear in my comment. You're right: the goal isn't to kill; it's just that no part of the goal involves avoiding killing.
Maybe he just had trouble concentrating. I heard there are camps for that too.
Don't use Blowfish.
https://github.com/mgreau/docker4dev-tennistour-app is a good example of using Java EE 7 / Angular application to show how to use Docker for Java Development

Arun Gupta wrote many excellent posts on how to use Docker to build Java apps: http://blog.arungupta.me/docker-tooling-eclipse-video/ on Eclipse tooling for Docker, http://blog.arungupta.me/deploy-wildfly-docker-eclipse/using Wildfly

https://github.com/chanezon/docker-tips/tree/master/orchestr... is an example leveraging Docker Compose and swarm for a Spring Boot application.

I hope these helps get you started using containers for development.
> JS/frontend world is the worst offender when it comes to engineering robust software

I completely agree. I still can't understand why the language that we depend on for increasingly large-scale front-end work still works like this:

[1, 10, 2, 21].sort() // returns: [1, 10, 2, 21]

It's 2016, software engineering is purported to be a profession, and we still have the worst tools imaginable.
You can contact amazon to get rate limits increased if you have the use case
What? Why would they care about a billion dollars? They're sitting on around $200 billion cash.
That scenario in the last paragraph is an uncomfortably convincing view of the future. Do you think it could be avoided by an additional step like the following?

Step 5: a mechanism for curated metamodules

This would not have changed much for the current situation, but it might help cultivating a "too important to play it fast and loose" mindset that would.
There's where git-vendor [0] comes in place!

[0]: https://brettlangdon.github.io/git-vendor/
One thing hosting providers could do better would be to split the risk a little by not handing the same dns server name to every client that chooses to have the hosting provider supply dns services.

The reason this might have some upside is that DDOS attacks against a specific DNS server are often intended to target one specific customer of a hosting provider. The attacker doesn't care about the side effects...just the original target.

Say, for example "controversialblog.com" is hosted on DO, and uses DO dns servers. The person attacking "controversialblog.com" looks up the NS records for the domain, and attacks that DNS server. The fact that it's one hostname that serves all of DO is of little interest to the attacker.

So, if DO would come up with say, 10 separate hostnames they could hand out, then this sort of thing would take down 10% of their customers instead of 100%.
The LinkedIn Data Center 100G Transformation
It used to be. I remember "back in the day", windows 95/98 had it. It wasn't perfect, but it was decent with a bit of training such that you could dictate reasonably well.
City Run London – 16th Century Adventure on iOS and Google Play