skysight-inc/HackerNews huggingface dataset:
While well intentioned as an abstract concept, all discussions around agile as a business concept to me inevitably lead me to conclude that agile sits somewhere between a cult and a cargo cult and that anyone drinking that kool-aid will at some point in the discussion run across no true Scotsman fallacies.
It has? I have Chrome version 51.0.2704.106 m (64-bit) and I do get the task manager with SHIFT+ESC, with numbers for each tab and GPU and for some extensions for CPU, network and memory.

What you link talks about chrome://memory, which was indeed removed, but the parent post only says

> You can use Shift+Escape for that
You can remove the judgement call by making it a design rule, as extreme programming did long ago. When you've duplicated something 3 times, it's time for some abstraction because you have enough examples now to see what needs abstracting and what doesn't. The problems you're describing are just symptoms of premature abstraction. Abstractions tend to fail when they come before the concrete, they tend to succeed when they were lifted out of several examples of the concrete.
Been bitten by this in React using ES6 where we would sub-class components and override render to provide another layout (or whatever; change behavior).

The right way to do it in React is to define a new Component and make the Component you'd like to depend on wrap around the returned JSX in render instead. Probably not a revolutionary paradigm, but it has made me better at reasoning about and structuring React components.
Get All Focus on Your Eyes with This Simply Tool
Why it's important to optimise the tricky parts of Ruby [video]
Sort of a tangent, but I always liked this quote: "It is better to have 100 functions operate on one data structure than to have 10 functions operate on 10 data structures." - Alan J. Perlis
I think the problem here is with inheritance, which I personally consider a code smell. There are few specific places when you need it, and by using inheritance there you're strongly signalling a particular abstraction happening - one of the "is-a" type. It definitely should not be used for just code deduplication.
Monorail: Light rail transport is common, as are elevated trains. Whether they use one or more than one 'rail' is beside the point.

Moving walkways: Escalators. They are everywhere.

Pneumatic trains: Ok, this one failed. Compared to modern electric options, the sealed tube concept remains a pipe dream. Hyperloop is fun to talk about, but I cannot see any market.

Single-person car: They are everywhere. We call them motorcycles. And I see old people in wheelchairs/scooters with roofs, walls and even doors. Single-person motorized transport is a thing.

Jet pack: Come on? Nobody ever took that seriously. Even if they energy density issues were addressed, the inherent dangers of such flight would prevent any widespread use.
People who think philandering is a flaw are not as enlightened as Einstein was.
Datadog security notice
Einstein was probably better at science than at debating social racial issues. Likewise, nobody should give more weight to Einstein's opinion on God, bees [1], or the Jews [2], than on anybody else's.

[1] http://www.snopes.com/quotes/einstein/bees.asp

[2] https://archive.org/details/AlbertEinsteinLetterToTheNewYork...
I hope we will one day see the stupidity of using 1t vehicles to transport 70kg humans around our cities at an average of 20km/h (on better days).
>The police does have a vested interest in making the public think that turning the phone off is pointless.

An interesting point, but...

If I were a criminal (I am not), and I were going to commit a crime (I am not), and I knew turning off my phone was pointless because the police can still track it, then I would just leave my phone at home, or give it to a friend.
"Brush your teeth" is dangerous advice if improperly applied.
It's not empty of content, it is devastating to your argument. Check out the upper bounds among these packages http://hackage.haskell.org/user/BryanOSullivan e.g. http://hackage.haskell.org/package/wreq ... there are some, same as there are some for e.g. http://hackage.haskell.org/package/http-client . Not that I approve of this.
> Now that memory errors are slowly disappearing, it's integer problems that are becoming the pain-in-the-neck for exploits

What fraction of integer overflow exploits crucially have to be combined with an unsafe memory model in order to be weaponizable? I suspect the number is close to 99%.

(I know there are a handful of overflow-related security problems that are independent of memory safety--someone mentioned money overflow issues in online games when this topic came up last--but they are few and far between.)

> I was quite disappointed when Rust opted to keep the wraparound model.

That's oversimplified. In debug builds, Rust panics on overflow; in release builds, Rust may or may not panic. It doesn't right now out of performance considerations. That is not a decision that is set in stone if the performance becomes acceptable in the future.
> - Perhaps job boards are slowly dying as a way to fill jobs

There certainly seems to be a new class of job site. Hired, underdog, and greenhouse are what everyone seems to use these days. With the exception of angellist, nobody I know hires using boards (though that's a small number of data points, since most of the people I know are front-line types that aren't in charge of hiring)
It's not just contracts and regulations.

Example: Bob the sales manager doesn't want to view reports through your handy web portal. Bob wants them formatted in Excel sheets, zipped, and emailed to his corporate Exchange account daily. Bob is the only person in the whole company who doesn't like your portal, but he is powerful enough that his whims automatically become mission critical requirements. You either give Bob what he wants, messing up your clean design to implement functionality just for Bob, or you have failed to meet the business's needs and will lose the contract, end of story.
Previous discussion: https://news.ycombinator.com/item?id=11032296
That's one issue, needing a canopy. The other is they are mechanically delicate, they wear out and need constant maintenance because garbage, dust, gunk, rubbish etc contribute to wear as well as breakdown. Just not good for outdoors environments.
It's expensive and provides few (if any?) advantages over conventional rail. Especially these days with safety codes such that you need to provide a way for passengers to exit the train in an emergency.
Only remotely operated flying vehicles are drones in the eyes of the American public.
Teenagers are mean.
I've purchased Feather and Derby blades on Amazon and they're stupid sharp. Which brands have you had bad luck with? Assuming DESR here.
Tech workers think Silicon Valley and startups are losing their luster
I very much agree with the liability responsibility and liability argument that you're raising. I also fully believe self-driving car makers should be 100% responsible for accidents and hacking incidents of their cars and they should fully compensate the victims of such accidents and hacks.

However, I think this is generally a good thing. When Android has 50 different OEMs (or whatever the number is), then some standardization is a good thing for the user.

You don't want Samsung or Huawei or some local Turkish OEM, or perhaps even the retailers themselves (as we've often seen with malware on imported Chinese phones) to start loading up certificates in a device before selling it. Think about what Lenovo and Dell, or all the anti-virus companies, are doing with their own certificates to PC users because Windows allows people to install their own certificates.

Also, in some countries, such as Kazakhstan, they want to start requiring users to download the "national security certificate" and install it in their devices.

This policy would prevent all of those things. That doesn't mean we still won't see CNNIC and Blue Coat/Symantec and other untrustworthy certificates loaded up by default in all Android devices (which you can still disable yourself), but I think overall this is still a good move from Google.
The reward for mining Bitcoin was just cut in half
But those efforts are mostly focused on the big asteroids that wipe out huge areas, right? Spotting an asteroid the size of a minivan or so is really hard, but if something of that size hits a city, thousands die.
Not feasible as all governments of this planet suspect one another to use the captured meteors as ballistic weapons.

Also planetary defense needs constant maintenance, so what if there is some crisis, and a prolonged downgrade of civilization?
Congratulations, that's two spaces on the "arguments white people make" bingo card.
Data Elixir 87: Data Science Portfolios. Python Tips. AI  MS. DataViz  NASA
That's really amazing.
So I've always had this (entirely crackpot) idea that the Tunguska Event is actually the place and time in space/history that you'd want to test the first time-travel device to. From a 'test system' design perspective:

- You'd want it to be somewhere isolated to avoid casualties, especially if there was a radiation risk (which you wouldn't know).

- You wouldn't want people to be able to analyze the immediate wreckage with any kind of high fidelity because there might be signatures of whatever you sent back (or however you sent it) that might change the course of history/technology.

- You'd want there to be fairly detailed recordings (ideally photos), and for it to persist into modern history, not just be a weird anomaly of 'the past'.

- You wouldn't want it be interpreted as some kind of military action.

To be very clear, I don't actually believe this is what happened, but I quite like the idea...
>they would be more easily understandable in many cases if variables were more carefully named

A mathematician already knows the notation, so a a long mathematical expression with descriptive names will not make it more easy to understand (if you know the notation). I would argue that it can even make things worse and add cognitive load.
That situation could have been handled better (from what I've read the deaths were all preventable by proper treatment), but even 16% lethality compares pretty favorably with the 100% lethality of a bomb.
Exactly.

That said, I think "give us the perfect requirements up front" is a reasonable defensive reaction. Because the first thing a lot of developers get asked is "When can you have this done?"

In most places, if the (made up, arbitrary) deadline is not hit, it's not managers who say, "Damn, our bad; we should have been clearer about what we were asking for." It's almost always an inquisition into either a) why the estimates were wrong, or b) what's wrong with the developers that they aren't delivering on time.

I now have a bag of tricks for keeping this kind of trouble to a minimum. But I think managers and execs have to stop asking, "When, to the exact hour, will this (hazy and ever-changing) thing be done?" It's not a sensible question, and if we pile blame culture on top of that, it's no wonder most projects quickly go off the rails.
As a member since July 14, 2009, I have nothing but praise for Pinboard. It does exactly what I'd like it to do and gets out of my way doing it. I've received tremendous value for money for my tiny fee.
Please don't post comments that react to nothing but a title. Those aren't substantive.
> And then you suddenly find yourself having a "god object", a class that does huge amount of things and most of them are not related to anything else in the class - they just exist to facilitate code deduplication lower in the inheritance tree.

No, you don't. Point of fact if most of the subclasses are duplicating some code, it does relate to what the superclass is and that code belongs there. This is not a god object.

> And then, one page really needs a different version of a behaviour that's common to many of them, and you're back to either duplicating or polluting the "god object" even more.

That's what overriding is for.

> Inheritance is a bad tool for this problem. It's better to separate different pieces of functionality and then compose them in views. If your view needs a component behaving in a slightly different way, then you can just create a new component (or even subclass the old one, if you must).

If composition is possible, it's always a better choice than inheritance of course; when it isn't, a shallow inheritance hierarchy is fine. Deep hierarchies are never ok.

> (or even subclass the old one, if you must).

No, you don't subclass concrete implementations to change them, that leads back to the whole problem you're complaining about. Implementations should never descend from other implementations.
Medical Devices of the First World War
Einstein signed a letter that strongly criticised an emerging political party in Israel. How is that "an opinion on Jews"?
They say in the article around half their yearly pay is in the form of bonuses from completed sales.

I'm sure it looks a lot like commission.
Just charting the world population by latitude shows that we're still living in a relatively narrow area of the planet where conditions are just right.

We're flexible, but still very tied to a fragile ecology.

1. https://goo.gl/images/bGCPHr
...That is literally what he just said.
UK PM candidate Andrea Leadsom thinks all websites should be rated, like movies
Oh boy. I didn't realize that type annotations in Python are that atrocious.
I thought they're a similarly elegant construct to Erlang's typespecs (or
ML's/Haskell's type declarations, which were earlier).
Maybe Tunguska event was first time travel that failed badly...
You don't make programmers work 60-80 hours [1].

It is possible, though, to find people who will work much more than 40 hours a week on their own if you let them, but that is rare and I'm not aware of any way to actually find these people.

I suspect that such people are less common now than they used to be, because of the internet, open source, and the generally greater availability and affordability of technology.

I was one of those people back around 1990. I was interested in firmware and embedded real time multitasking kernels, and found a job where I got to basically play around with whatever interested me in these areas. Several times my boss (who was also a close friend from college) had to force me to leave the office and take a break, because I wanted to keep coding, or keep writing the engineering part of the proposal for the next project we wanted to bid on, and he was worried because I'd been at it already for 20 hours straight that session. And yes, I was productive during these long hours. Over the course of most projects, I averaged several hundred lines a day of debugged, tested C code.

I believe that there are plenty of programmers today who put as much time and effort into technical things today as I did back then...but instead of it being 60-80 hours for the employer, it is 40 hours for the employer and the rest at home for the programmer's hobbies.

In 1990, to do the things I was interested in you generally needed to find a job involving them. Nowadays, you can get one of the numerous inexpensive cheap SOC computers (Arduino, Raspberry Pi, TI LaunchPad, and many more) and high quality complete free tool chains, and do all that at home on a small budget.

Basically, in 1990 doing nerd things in a big way generally required getting a job doing those things. Nowadays, you can do nerd things in a big way as a hobby. So someone who wants to spend 60-80 hours a week on nerd stuff no longer has to find an employer that will let them do it...they can spend 40 hours at their job, and then 20-40 at home on their own.

[1] You can make them spend that time at the office, doing things that look like work, but generally you won't get any more net useful work out of them than if you had just had normal work hours.
>I googled "most popular people in America" and Google shows me pictures and out of the top ten, half are African-American including Barack Obama, Michael Jackson, Muhammad Ali, MLK Jr, and Oprah Winfrey.

Try googling "over-represented race in incarcerations", "over-represented race in police shootings", "redlining", poverty stats, etc. too. Besides, of those popular people, Michael Jackson tried to turn himself white, MLK Jr was conveniently murdered, Muhammad Ali was persecuted by the state, and Barack Obama is routinely called racist slurs despite being the president.

Plus, it's easy to make popular idols of talented black artists and still view down on the majority of them. Louis Armstrong, boxers and other black entertainers were quite popular when the country was openly racist too.

>Many slavers were African

But none of them operated in the USA or kept slaves there.

The buyers of the millions of blacks that came to the US, those who used and abused them as slaves, and who made the trade profitable in the first place, were white Americans.

>Many slavers were African, and in 1946 very few Americans would have had ancestors who were either slave traders or slave owners.

No, but the majority of them had ancestors that were racist, enforcing double standards, unfair laws (segregation, Jim Crow laws, etc.), and in some cases violence (beatings, lynchings, etc.) to the black population. And most of them were racism themselves too.
From bad to worse. Why not just call it Turing?
> Looks like the shockwaves were the primary mode of injury

Not the shockwaves, but things damaged/knocked over by the waves. If you were standing in a field, the shockwave would do nothing to you. It was harmless. But if you are standing beside a poorly-designed glass building, pieces are going to fall off that building. This was Russia. I would expect that other countries, with different building practices, might suffer far fewer casualties.
This is also something Paul Hawken touches on in "Growing a Business", along with a suggestion (IIRC) not to pay sales staff a commission:

https://www.amazon.com/Growing-Business-Paul-Hawken/dp/06716...
In the 1860s, black people were slaves. In the 1940s, they weren't. Obviously, no further progress needed to be made.
With how partitioning works in Postgres you could easily have millions of tables (even though they are just copies of a parent). I remember a company in Austin writing a blog about how they delta which such a large catalog size Postgres.

We have about 200 tables that we partition by day. So in three years it's 200*300.
Haha, I should have proof read that, what a terrible sentence I wrote there :)

My wife's an engineer there and enjoys her work. Her team seems to be a smart and fun bunch to work with, and the hours are pretty ok. The only times I've seen her working extra were because she wanted to, not because she had to.
I don't play any card games, but what's honestly the big deal? Is the game about card-collecting skills, or deck-building and play strategy? It's hard to argue the latter and ban people for not having an original version of a card. I guess I don't really "get it", or I had way too much fun playing ridiculous mods (where it was fair because everyone had equally ridiculous stuff) for games (Mr. Pants Excessive Overkill for Quake 3 comes to mind). IMO it'd be fun to play some Magic tournament with all fake cards, so everyone could build their dream decks, then see who was better at building the best deck and better with play strategy.
In Amsterdam speaking English is well accepted.
The code that took America to the moon was just published to GitHub
FYI Codename One works on all of them natively.
Notice I didn't refute or try to refute your claims. I just specifically mentioned that on the most or second most significant platform C++ is not a first class citizen.
How to model SaaS churn for experiments
Without the broadcast flag how would networks agree to support HD? https://www.eff.org/deeplinks/2009/06/dtv-era-no-broadcast
... and how do you know which one is of high quality when you buy?

Since the products are copies -- how would you know you don't get ripped off next week, when Amazon sell some other copies? The packaging etc look the same, by definition...

It is just not realistic to keep up with the exact details and doing a complete quality check whenever you buy anything, from toilet paper to cars. Every time.

I predict that this is just a short phase. If the quality of products at Amazon will be a total dice throw, the consumer reaction will be to buy directly from the producers' web sites. That is not in Amazon's interests, so they will soon be more transparent. Or become irrelevant.
How many -stable patches introduce new bugs?
TOGEL ONLINE TERBARU,AMAN DAN TERPERCAYA
(( http://www.forumsgp4d.net/ ))
TOGEL ONLINE TERBARU,AMAN DAN TERPERCAYA, kumpulan daftar situs betting togel online singapore/hongkong terbesar dan terbaik.
Has a very precipitous downturn in VC funding actually occurred? There's been convincing clatter for awhile now that it's expected, but my feeling was that while it was lower, it wasn't the kind of downturn that would shave 40% off the hiring market.
Similar software for matching parse trees:

Tregex: http://nlp.stanford.edu/software/tregex.shtml
tgrep2: http://tedlab.mit.edu/~dr/Tgrep2/
1) Tranquilizer darts aren't magic. Without calibrated dosage, the effects can range from nearly nothing to fatal. [1]

2) Tranquilizer darts work against unprotected skin, not heavy clothing and certainly not against body armor.

3) Where would one get a robot armed with a tranquilizer dart launcher? They're not exactly off the shelf items.

[1] https://www.quora.com/Why-dont-cops-use-tranquilizer-guns-wh...
Show HN: Add test coverage to your ES2015 codebase
Perhaps I haven't explained my idea very well. I'm imagining millions of small robotic spacecraft, self-constructed by self-mining asteroids that they have found on their own. The little asteroid spacecraft would roam the solar system on huge orbits and search for potential Earth impact-bound objects. If it finds something, over the course of hundreds of years, or thousands of years, the network of small asteroid spaceships could send a probe to the offending target and adjust its orbit so as not to impact. It could then use the offending targets to create new nodes in the system. Theoretically the defense network could last as long as the sun does.

I do agree that the law of unintended consequences might mean that building such a system would instead ensure the destruction of the Earth rather than save it. But it's an idea.
You've got the right question to see if this datapoint matters at all.

I don't know the answer unfortunitly, so I'll answer a much easier question instead: Only 46% of US children are in a family with two married parents.
nice idea. I would prefer if it reset to 0 on page load though. I used it for a few minutes and after a few pages the count was already in the hundreds, at which point I've lost my sense of whether the count was increasing for this current page or if it was already high from previous pages