skysight-inc/HackerNews huggingface dataset:
Another useful rule: if you find yourself needing to change an existing abstraction, especially if you need to make it more complicated by (say) adding a parameter, this is often an indication that your design is broken, and that you need to change that so that you don't need the extra parameter. Most often in my experience the root cause of most problems of this sort is different data representations. Something is big-endian over here, little endian over there. This quantity is represented as a string over here, as an integer over there. I've found that being absolutely ruthless about being consistent in data representations goes a very long way towards keeping my code from spinning wildly out of control.
A previous discussion: https://news.ycombinator.com/item?id=11650712
Out of 108 unicorns 78 are from the UK only nine are from Europe.

http://graphics.wsj.com/billion-dollar-club/

The US is expected to take over Germany soon in export for Denmark.
I use something like this which i wrote myself years ago, but i still use it every day. My version is called qgrep (for quick grep).

It does this:

* knows which files are source code and which are not
* ignores tmp files like ~ and #
* automatic recursive search.

Some differences from ACK which i still want,

* can be given a filename pattern and can glob within each directory.
* can search binary files too!
* doesn't do regexp at all!

> why?
regexp is much slower than straight string search if using something like Boyer-Moore-Galil, and this is important when you're searching massive subtrees of files.

For regexp, I'll use grep with its fancy options. For straight, find this string in all my code, I'll use qgrep.

For those linker undefined, mangled functions, it's great to qgrep the .o files and .libs.
This is the exact reason we have a justice system with courts and rule of law rather than supporting vigilante justice. If you remember, early on in this incident, a completely innocent individual was identified as the possible shooter with many absolutely convinced he was.

https://www.washingtonpost.com/news/morning-mix/wp/2016/07/0...
I find it quite annoying that we can't say "retarded" anymore but "autistic" and "autism" are valid insults. This has a lot to do with high-profile autistic people such as Christian Weston Chandler, who have a whole host of other psychological and emotional damage that has little to do with autism itself. They are the ones who wear their condition on their sleeve and try to use it to excuse all sorts of reprehensible behavior. Until in the public mind the words "autism" and "Asperger's" become associated with cringe.
Kids these days. Back in my day, wife code was forever /s ;)
Completely agree with the Sigma thing. I found the PUA stuff (my interest was more evo pysch) so frustratingly irrelevant and misguided until I read about the Sigma reproductive model. I think the difference (clinically speaking) between narcissists and aspergers is the need for admiration. No one I know with aspergers wants any attention, basically ever. I think Jobs is more of an INFJ narcissist. As opposed to more borderline INTJ (Aspergers).
That bad culture is a separate problem which will make everything worse.

In your case, it seems mixed - while you do have to update code in multiple places the flip side is that you can more confidently change code in one location without breaking something else. If you're on a death-match piling up technical debt, that might be less painful than dense inter-connected code, albeit still worse than working somewhere with more long-term thinking.
I think a lot of commenters here are missing the point being made in the short story.

Agile is good for startups building a product where they don't already have a known product/market fit. It's understandable in that situation.

A client of mine uses it to unburden itself with upfront design for a 3rd gen system that is well known and could easily be built with waterfall. There have been (what I would call) two false starts already. I don't see why agile is beneficial in this situation.
i believe delicious is free so you'd still need to convince those users to switch to a paying model.
Everyone is accountable
The Noise None of Us Can Live Without
Keep in mind that glaciers always melt. And cause landslides. And new ones form. Been happening for millions of years.
"Don't succumb to early optimization" applies as much to design patterns as it does to algorithms.
I thought it was going to be FidoNet or Compuserve.

My first email was via Bluewave, propagated BBS to BBS
I signed up back in the $9 days, and currently have ~7k bookmarks on onboard (flawless import of my delicious data, too).

It's one of my everyday tools, and would pay a monthly fee if it ever gets to that.

A perfect example of "do one thing, and do it well".
This is why I canceled my subscription. Decidedly half assed support. I'm aware of pipelight, recent versions of chrome etc.
I upvoted again because op said he wanted to get back into C++ and I agree Scott's book is exactly the resource for this purpose.
Related blog post: http://blog.ayoungprogrammer.com/2016/07/natural-language-un...
I doubt he had hard armor plates that would stop a rifle bullet, and they're heavy, so their coverage is pretty small.

More likely there just wasn't a good shot to take of him, the only question is why not wait him out, and the threats of bombs and the fog of war (and this was much closer to war than any incident in recent memory, it's reminding me of the cultural '60s and those who wouldn't let it go into the cultural '70s) made it reasonable to take a more serious although not necessarily deadly methods (it's not like they used a fragmentation grenade) to stop the threat he potentially still posed.

And given his was a lot better at close quarters combat than his opponents in general (http://bearingarms.com/bob-o/2016/07/08/video-suggests-cop-k...), storming is position is not something I'd ask anyone to do.
It is amazing how both adaptable and yet resistant to change we are. We are so afraid of change—yet what comes just might be better than what we have now.
If he is a credible and imminent threat (where imminent is immediate, requires similarly immediate action to protect oneself), then I wholly support neutralizing the threat.

I think that police are increasingly reaching for lethal force without exhausting nonlethal options.

I also think that, in this instance, he was a credible but nonimminent threat. So in that sense, yes I would object to shooting him.

A nonlethal response to continue containing the suspect, even at some risk to themselves, would have been more in line with the duty I believe police officers have. Minimizing the risk to themselves will not maximize the fulfillment of their duty (which is obviously true because the extreme is them never leaving the station, etc). I do not claim to know what the right balance is. However, I would argue that as public servants, their duty inherently necessitates taking on some level of risk in order to uphold our values of justice. Our values of justice require that they not kill suspects they are tired of dealing with - they must stand trial.
> Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.

> Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.

http://agilemanifesto.org/principles.html

It sounds like the system started off as agile and the second system lost the plot.
I haven't looked at Pocket for a long time, so I don't have a meaningful opinion to share. The scenario you lay out is exactly the kind of thing I wait for. It takes superhuman effort (or laziness) not to make gratuitous changes.
I'm not sure I understand this example. Signals allow the program to receive a notification whether they are blocked on I/O or running on the CPU (and receive it immediately in the latter case).

The application can integrate signals with its event loop with the self-pipe trick, or it can use Linux-specific APIs to have signals delivered over a file descriptor.

http://man7.org/linux/man-pages/man2/signalfd.2.html

I'm not saying signals are fun, but I don't think you've proposed anything different/better.
There is a fine line between short code and readability, which is, by far, one of the most important factors of code quality. Say you have a code:

$this->executeAfter(5);

This is a short code, but it's not readable. What the hell is 5 here? Let's improve it a little bit.

class Time {

protected $seconds;

private function __construct($seconds)
{
$this->seconds = $seconds;
}

public static function inSeconds($seconds)
{
return new self($seconds);
}

}

$this->executeAfter(Time::inSeconds(5));

I've just added ~10 lines of code, but the readability of executeAfter is way better. In addition, the executeAfter method is more flexible, since it can manipulate the Time object now.

This is a very basic example to illustrate what I meant when drawing a line between the short code and readability.
The point is more that by saving those 15 minutes, it's a cumulative saving for all future use cases. Though, I don't think I fully agree with this in all cases. It can be hard to predict when something really is going to be used often enough that this is important.

IMO you build the minimal thing that does the job, then after understanding the use case go back and refactor to deal with the accumulation of 15 minute pain. Doing it right at the beginning is the definition of premature optimization.

And on the topic of building new, this is a mistake many developers make: that it's easier to build new, then to refactor existing. What they fail to realize is that the old code they think is too difficult to maintain is battle tested, in production, has operational understanding associated with it. All software goes through this cycle, and so while it's fun to build something new, you are inviting debt while doing so b/c of the unknown production issues and edge cases that need to be figure out after it goes live. It's not always wrong to rewrite, but IMO, it's a last resort. BTW, this is why SOA is important: strong defined contracts/APIs between services allow for components to be replaced with a higher degree of confidence.
HOLIDAY DESTINATIONS IN NAKURU KENYA
> They are comparing the ratios of armed suspects to unarmed suspects being shot by police, so perhaps they thought that was sufficient in factoring in the prevalence of guns.

I'm not seeing why ratio is important compared to magnitude. There is certainly a relationship between number of armed suspect shootings and number of unarmed suspect shootings but it is not clear what that relationship is. It can't be a constant, that just doesn't fit human threat response. Rather, I would expect that the higher the armed suspect shootings (numerator) in an area, the smaller the ratio, meaning that nonproportionately more unarmed suspects are shot as a direct result of a large number of armed suspect shootings. But if that's the case, that will increase the likelihood of unarmed suspect shootings without there being any necessary racial bias. A smaller ratio just reflects a larger denominator increase due to numerator.

If we have equal numerators for each race, but the denominator differs, than that seems like a clear indication of racial bias. But if the numerators are different at all, that potentially reflects an entirely different police interaction dynamic. The expectation that one race is more likely to be armed than another race is, strictly speaking, a racial bias but could also be a rational bias based on encounters rather than prejudice.

What are the numerators? This whole issue may be of course be misguided but I'm simply unable to find the actual numbers from the paper.
If you're interested in the methods and related questions, check out this (4 part) youtube talk: https://www.youtube.com/watch?v=xG79jpAYxmQ&index=7&list=PL5...
Ha ha yeah, I came back to look and saw that interesting typo. Whoops.
Absolutely not, and he had a SKS (https://en.wikipedia.org/wiki/SKS); military weapons, especially ComBlock ones, are built with tolerances to allow continued function as they get hot, generally at the cost of accuracy.
For some categories where Amazon sells its own brand (which keeps growing), I wonder if this benefits Amazon.
Agreed, which is why I always disliked the show "Robot Wars". It sounds better though than "Giant Armored R/C Vehicle Wars".
A Startup Shies Away from the Gig Economy
I can't remember who said it, but I remember someone saying there was one question you should ask yourself when reading any news story... Why am I reading about this now? In other words, for what purposes is this story being shared right now?

I'm not suggesting there's a conspiracy behind every story, and there are often benign explanations that can coexist with dramatic ones. What I am suggesting is that question is a vital one for seeing through media spin, regardless of whether it's intentional or unintentional.
We need to talk about AI and access to publicly funded data-sets
This looks really interesting, is there a reason why it hasn't been uploaded to the Chrome Store? It would be much easier to install and keep updated.
The slowness of the robot is a good point to bring up and a pretty strong counterargument because it indicates that the robot was only useful in a situation where the police perceived[1] that they had control of the situation.

[1] remember, if we're talking about what procedure police should follow, we have to think about the perceptions that they are responding to.
This is an very important concept, "premature abstraction is bad"
It seems nobody mentioned it yet, but what happened to the Apply HN "winners"? Did anything come out of it?
He wrote FAT on an airplane.

Make of that what you will.
that's one competitor i'd keep my eyes on. so far their implementation is pretty flawless.. let's hope they get lazy
Shift + Esc doesn't seem work for me (Chrome 53 dev), and there are a few open bugs about the shortcut not working. Opening Task Manager from the menus works fine though :)
Giving money to poor areas isn't actually proof of anything besides money is taken from some other regions and given to others. Who gets what in the EU is purely based on the various countries and organizations ability to make the most out of it.

Denmark had an area which spend billions subsidizing various efforts with EU money without any success.

So while that might be great for the local community getting money from the EU isn't a sign of anything besides the EU gives out money based on your ability to get money of out the EU. It's not based on some system of fairness or priority.

The pound is not going to collapse just as little as the Danish krone did when we decided not to be part of the Euro. Back then the amount of scaremongering about what would happen to Danish economy was insane, yet Denmark is one of the countries who fared best after 2008 and still have tripple a rating.

The EUs funds are largely there for the taking. If you can make a case based on some vague notions you can get money from the EU. That can easily be solved by the individual countries instead.
Not exactly, though inspired/reacting to that approach. The reader view is based on this: https://github.com/mozilla/readability
I dont think police are paid enough to risk their lives against someone who is actively trying to kill them. How much would you want to approach a situation like that in the way you are all detailing?
You have to wonder when a large piece of space rock will hit somewhere inhabited. That said, with 3% of earth's land being urban (3% of 29% of Earth), and reasonably infrequent falling rocks, it's really not that likely to happen in any given lifetime. I suspect we're keen enough these days to be able to predict and evacuate the right areas, though. This paper references another that suggests a "Tunguska Event" is a once in 200-300 year deal:
http://articles.adsabs.harvard.edu//full/1994Metic..29..864Y...
(Man I am so far into the rabbit hole now)

Looks like 15th century China had an event that probably had a number of casualties (though apparently modern researchers dispute the details). Wasn't aware of that.
https://en.wikipedia.org/wiki/1490_Ch%27ing-yang_event
FREE E-BOOK: How to Get Your First 10.000 Instagram Followers
I am a non-UK EU national in Britain, so I'm saying all this first hand.
For a long time I've thought that Don't Repeat Yourself is the most important software engineering rule. I still do, but in line with this article, I've learned that some things that appear to be duplication if you just look at the literal code actually aren't. Just because you've got a chunk of ten or twenty lines that are identical right now doesn't mean that they are actually identical.

It's hard to give concrete examples of such an abstract concept, but one I encounter with some frequency is some chunk of code that grabs something from a URL. Assuming you're using some half decent library that takes care of the brute mechanics, it's easy to end up with repetitive code to deal with setting up a form and putting on a couple headers and dealing with authentication or whatever, and it's tempting to try abstract on that yet further. Yet I find all the attempts to do so make the problem worse, because the superficially-similar code is actually quite dissimilar. The pressures on the instances are different. Here I may be deeply concerned about SSL, there I may be adding header hacks for some broken auth scheme, over there I've got some sort of serialization problem. Trying to put them all behind the same abstraction is just pain. It turns out the level of abstraction offered by these often years-old, mature HTTP libraries is more correct than may initially meet the eye.

For code to be "duplicated", the full context of the code need to be duplicated, not just have superficial visual similarities. It's important that all the code with the same context, the same evolutionary pressures, the same likely change planes end up in one place, and it is equally important that code that lacks that similarity not end up bound together. In the end, it's the same error.
I personally don't tolerate abuse and would GTFO, but I understand that's not always an option. :(
It takes time away from real work without making that work significantly easier to accomplish. It is frequently used as a tool of control by managers who want to be in charge, thereby defeating its own reason for existence. The terms and practices tend to be hokey and faintly demeaning.

The problem is not the specific body of techniques used to schedule tasks and manage time; the problem is the way that the hierarchical nature of traditional management structures diminish agency and discourage transparent communication. This leads to misapplication of effort and destroys motivation, crippling productivity.

Empower people to act responsibly and they generally will. Exercise empathy and people will trust you. Give people the information they need and they will reciprocate. Agile development was an attempt at doing these things better, but it has been reduced to a collection of code words and empty rituals by managers who don't realize that it is actually their philosophy about the purpose and nature of management itself that needs to change, and not merely their choice of techniques.
People are downvoting, but if her product is manufactured in China that's pretty much the reason her product was copied in such short order.
Because they're doing different things? Also clearly outlined?
Plaintext for randomness evaluation of cryptographic algorithms?
The site says that 75% of all bitcoins have already been mined. I understand that it will become more and more difficult ensuring that the amount of money will continue to increase. However, I remember that I once read that bitcoins can only be split into so many "pieces" which wouldn't be enough to provide a sufficient amount of money for the economy to function. Does anyone know more?

Edit: found the answer: The protocol allows to create new, smaller units. http://bitcoin.stackexchange.com/questions/122/will-we-ever-...
I found flights to Dublin on flychecker from € 50
That's some George W. Bush style exaggeration. A small conventional explosive is in no way a WMD.
And following from that I guess robots doing traffic stops in high risk black neighborhoods.

The only positive I can think of, from this escalating into totally unimaginable madness is the most cities dont have the budget for all this sci-fi shit.

I can't even believe Dallas had a bomb placing robot lying around.
Yes, he could read a spec and I read this before.

Dont get me wrong. I have a lot of respect for both Joel and Bill Gates. I just dont see this particular incident as anything special. Bill Gates didn't actually do anything except annotate the spec and throw some ideas out there.
Using the awesome Google benchmark [pdf]
If your family can't stay or can't develop their professional careers in the UK then yes, moving somewhere else is easier than a life full of misery and regrets.
Thanks for the comments, I don't find many people who are into this stuff AND don't have cartoonish views of people on the spectrum.

I wanted to share this next bit because you seem like you might appreciate it. At least it took me awhile to figure it out. :)

In my experience, Myers Briggs is most helpful if you think of all eight attributes as independent capabilities each person can have, and then rate each on a scale, say, from 1-10. From each pairing, the one with the highest value determines their type, e.g. INFJ.

So, I would agree that Jobs is an INFJ (let's say that all are "10s"), but that doesn't mean that his ESTP traits are all pegged at zero. Instead, you might say Jobs has E=5, S=2, T=8, and P=6 in addition to I=10, N=10, F=10, J=11.

Mostly what the dominant Myers Briggs type gets you is a way to determine a person's typical problem solving pattern. NFs feel (and get excited) about a solution first, then convince (think) themselves why it's right.

OTOH My wife is an ENTP, and she thinks things through first and then gets excited—the opposite of me. If I wasn't aware of the underlying dynamics, I'd get super frustrated every time I brought her some exciting thing only to get calm analysis and no excitement (at least, at first).
Was it just garden-variety tourist fleecing, or did you head outside the city centre? Vienna's definitely pricier than Bratislava and Brno, but I've never found it to be outrageous. Also since both of those cities are so close I don't think it's out of the question to be based in either and seek funding/investment in Vienna is it?
I have written an analysis of what might happen next year in Switzerland and elsewhere:

https://medium.com/@octskyward/ok-what-now-e3f64d38f7#.q4vch...

It is almost without question that the Swiss will hold another referendum in the coming months, as their deadline for implementing the previous referendum's legislation (which they are legally bound to do) will expire in February. However due to the latency on getting new laws through Parliament they really have to start now.

There is no way to renegotiate with the EU because the EU sees any geographically European population that chooses to defy the EU as some kind of terrorist, with whom negotiation is unthinkable. They refused to negotiate with the Swiss and are now demanding the Swiss join the EU proper or else there won't be any further negotiations (ever). The Swiss do not want to join the EU. So the stage is set for a showdown.

The best case outcome for the EU is a new vote in which the Swiss choose to continue the status quo for a little while longer.
I was pretty surprised by how much time was devoted to rebutting "everyone autistic is a good engineer" when all of the quotes cited (including the infamous ppt) were claiming "every good engineer is somewhat autistic".

I don't buy that latter claim either, and it's worth talking about how the "autistic programming genius" stereotype is harmful to everyone, autistic or not, but writing an article that's centered around committing the base rate fallacy doesn't mean much of anything.