skysight-inc/HackerNews huggingface dataset:
The author also misses a key point is that in pregnancy there are no shared resources -- each pregnancy is independent. In debugging hard problems this is often NOT the case.

For example, if you put 100 teams to find a particular issue that is causing crashes in the field you suddenly have your field team getting requests at random times asking similar questions, although each may have a distinct twist. At some point in time a percentage of the team suspects the networking stack -- the networking team starts getting questions staggered over time. Their time now gets spent looking at this. And then if you have to run some type of stress or in a specific customer environment -- that gets sequentialized, unless you buy new hardware.

And lets say all 100 teams find a fix, but they are all in different places in code. Now you have to figure out which is the right fix, which may not be a complete sequential process, but it's not embarrassingly parallel.

On the flip side, if you only want one fix, it's easy to shelve the rest (you could pull one of the other fixes back in if the select fix is found to regress something else). But if you only want one baby, and multiple couples have one, it's a bit trickier to figure out what to do.
Psp's non-standard standard library (for scala)
This experiment was different in some way? More 'neurons' this time? That qualifies as an experiment.
Here's everything non-techs need to learn coding. And it's fun
Dotdotdash, a morse keyboard
Then trucking companies can maintain their margins by charging more to haul goods. If there really is excess demand, then the market should be able to absorb price increases.
Dressmakers have it really bad in the UK, as when you buy fabric, the widths are in inches and length is in meters.
The sheer numbers are for the legions of ho-hum programmers building CRUD data-entry systems for e.g. aluminum can factories. The majority of startup-oriented engineers are a different group and I agree that .Net may be off-putting to them.
absolutely... problem is that I have to think hard to figure out how much a yard is, and you have the same problem with meters. That's what standards are for.
That was partly my point, at least for functional languages that can express these concepts, like certain statically typed ones.
Here it is. https://github.com/robbyrussell/oh-my-zsh/issues/377 (tl;dr seven-month fork that fixed over 100 issues)
Observer bias.
Ask HN: What do you use for Flask social/oauth login?
I'm using Flask to develop a project (https://github.com/rahimnathwani/measure-anything). I've used Flask for a few small things before, but this time I'm trying to do better by:

- Instead of having everything in a single .py file, using Python packages and Flask blueprints to make the code more modular.

- Having a way to distinguish between different users

- Tests (I haven't written any tests yet)

I'm using Flask because I find Python comfortable, and I was scared off by the amount of convention I encountered when I researched Rails and Django. Both Two Scoops of Django, and Michael Hartl's Rails Tutorial, are excellent, but the learning curve to having a basic project working seemed too long. Maybe I'm wrong.

Anyway, this is just to say that I realise I made a choice not to use a 'batteries included' framework, so I shouldn't expect social auth to be easy.

I've seen three different modules for social auth in Flask:

- https://github.com/omab/python-social-auth

- https://github.com/mattupstate/flask-social

- https://github.com/wooyek/flask-social-blueprint

Do you guys use one of these, or roll your own using Flask-OAuthlib?

I'm sure my ideal flow is pretty common: click a Facebook or Google button, click 'authorise', have the software auto-create an account, and then log me in. I'm almost there with Flask-Social; I still need to enter my email address and a password before the account is created, but I think I can fix that as long as I can get an email address from somewhere.
The First Barbary War is a fascinating subject, and it's interesting as a point of reference. Not that I'm necessarily advocating the bribe or tribute system, per se; I'm just thinking about it as an intellectual exercise. But in theory, a key difference between the US today and the US in the 1790s is that we have the world's most impressive and dominant navy, and if push came to shove, we could retaliate pretty aggressively. So our bribe would be backed by a credible threat: take this payment, but don't bite the hand that feeds you.

Now, as I mentioned, this creates all sorts of perverse economic incentives. First, it encourages infighting among the warlords, further destabilizing the region as each band or group jockeys for top position. Second, it could just as easily be taken by the pirates as a sign of weakness. They'll want to test the limits of that weakness, either by raising their prices over time, by taking more ships for ransom. Finally, it legitimizes some no doubt unsavory leaders, whose American ties would cause deeper sociopolitical problems for us when they got out.
Good! Tesla has pushed the big car companies to do what they could have done decades ago - build and distribute fully electric cars that are the same or better quality than non-electric cars. And, your questionable view that profitability for a company in it's growth phase defines success non-withstanding, they're pretty quickly eating their lunch at it too. They're going to continue to be forced to compete with Tesla because Tesla builds amazing cars that people want to buy. When they're able to sell them more places and build them at new price points (already happening), it's going to be fun to watch.

However, that doesn't mean the big car companies won't make cars that are just as good - the point is that now they HAVE to and that's good. Same with self-driving cars.
The fall of the FBI's most-wanted cybercriminal
Minimum viable prototypes should be built as quickly as possible to test your idea. If the market doesn't like the idea it doesn't matter what you built it in.
Show HN: It shouldn't take hours daily to eat right
It's because car companies don't want to take the a big bet and try to do it all at once. That's why every deal Google has tried to make with auto-makers has fell through. Google wants to rush to the finish line and create a fully self-driving car. But the time-frame to be able to deliver that is fairly unknown due to a number of issues.

Auto-makers want to do smaller R&D projects that they can deliver to consumers within a few years of start (instead of a decade+). Things like adaptive cruise control or self-braking. These are things that were just a few years of R&D and are shipping now.

They are different paths to the same goal. We don't know the outcome yet, Google or the auto-makers may get there first. But we do know that auto-makers will have sellable features in the mean time while Google just has pretty marketing videos and demos.

What Google is bringing (that the article mentions) is the discussion about fully self-driving cars. This discussions means laws are being passed to facilitate the technology. It also means that the NTSB, insurance companies, and others involved in the auto industry are talking about the impacts of what a self-driving car means within our current system. So hopefully by the time they arrive, the rules and laws will be caught up with it. It also means consumers are talking about it and becoming aware of the possibility, which helps motivate others to work on the same projects. It may also mean that consumers are less wary of the technology when it actually does arrive.
Elixir, Making the Revolution Fun
In the perfect world of the auto-correcting market.

In real life, in the case of coal miners and their "dead work" (necessary work that wasn't getting paid), it took bloody strikes and fights to get those rises, the amounts paid weren't automatically upgraded.

The "money required to attract X workers" only plays a role when those X workers are not destitute and starving to begin with. If they are, and the company can pay them less and still have a huge profit from their work, it'll do that.
The beauty of the old system was that it mapped onto the everyday experience of farmers. I am sure hundredweights and furlongs and so forth all made lots of sense. But units have to cross cultures and times — the only intuitive units left to boast about are the foot and the yard, which are 30cm and roughly a meter. Indeed, we are probably taller now than when the yard was defined to the extent that the meter is probably closer to an intuitive yard than the yard is.

Incidentally, the official definition of an inch is 2.54cm. Now that's intuitive.
Those jobs aren't different from any other. Some people enjoy installing and maintaining septic systems.
> Food stuff is bought in "dekos" (dekagrams).

Where? I've lived my whole life in a metric-using country and I'm fairly sure I have literally never heard of that unit until just now...

Our food here is all in grams (i.e. a 100g packet of chips, 300g steak) or kilograms (1.5 kilo bag of rice).
The main problem with all arguments for keeping the prices of books (and other information sources, for that matter) high is that they are bullshit. If we look at the history, the price of books were never depending on their _contents_; instead, it were always determined by their _production_. Hardcover books, on high quality paper and with colour illustrations, always were priced higher than low-quality prints with b/w images (or without any) -- and the price was never significantly affected by the popularity, a paperback copy of "Harry Potter" or "50 Shades of Gray" costs essentially the same as a unknown author's book. And the price of books was always affected only by technology improvements -- Guttenberg's press, linotype, print-on-demand etc -- and not by anything the authors wrote about.

With digital revolution, the book production costs drop essentially to zero. Also, most of the elements that used to be necessary to bring a book from an author to their readers -- agents, typesetters, printers, bookshops and especially publishers -- are becoming redundant; authors can easily market themselves to a worldwide audience, distributing e-books directly to the readers and even directly accepting payments. The only thing preventing this is the publishers who push against it and try to keep as much of the status quo as possible, as Hachette is doing now.

That being said, Amazon is not without their own part of the guilt, as they're trying to become the central place for locating and distributing books, and so far they're succeeding; but that is a whole different issue.
Perhaps that's true, but my sample does indeed include quite a number of startups whose stack is built on .NET. Their engineers are usually much less experienced (and are often lacking theoretical foundations. E.g. they know how to use MS tools without knowing how stuff actually works) than those of typical SV startups.

I'm sure there are good .NET engineers out there, but hiring/finding them is more like finding a needle in the haystack.
In fairness, I don't think $100k buys you the opinion of the NYT. I give the paper a little bit more credit than that. Besides, it's been airing this blow-by-blow for months now, long before that ad buy.

To the extent the NYT is inclined to take Hachette's side of the fight, that's largely because its staff and editors are much closer to Hachette, geographically, professionally, and socially. It's still not a great reason, of course, but it's not pay-for-play.
Temperature certainly has an effect on batteries¹. But also that the periods of high current demand were spaced so far apart -- the batteries had time to recover. Much like how the battery in your car is a "starting" battery -- high current is needed only occasionally to start the engine, with the alternator making up the demand the rest of the time.

¹ Dad used to work for Union Carbide, which owned the "Eveready" brand at the time. One of the projects he worked on was a battery for the Union Pacific Railroad. It was designed to be buried in the ground in remote locations to run signal systems. Burying it gave it a more constant temperature. If the researchers placed the battery on the inside of the collar next to the wolf's fur, that could really extend it's life.
I think that is typically called "pythonic".
The Master, The Expert, The Programmer (2007)
$619B missed from federal transparency site
I think this guys comments are being unfairly downvoted. I also expected some interesting Angular stuff going on given the link title.

It does look nice though and I have bookmarked it for future reference.
Quite a few of the replies are practical, but unfortunately reality isn't always practical. Instead we often use technology for signaling, and the truth remains that the Microsoft stack (even if you talk up open source equivalents like mono) is an anti-quality signal. This is not judgmental (I have used and abused the MS stack for years), but is observational. And that tendency is often based upon experience -- the bulk of .NET programmers are enterprise inhouse developers usually building dated, poor quality solutions.

This hits hiring as well. Someone mentioned the quantity of .NET programmers, and while this is true the quality is extremely, extremely poor on average. Having had to hire .NET programmers, the best success we have had, result wise, is to hire !.NET programmers (e.g. the hiring process started being about abstract problems that could be solved with anything, etc) and let them loose with C#/etc. If we limited ourselves to the .NET skillset we got tonnes of applications, almost all of which were terrible.
Nor is I even Qt! It's a web view.
New mobile game from the creators of Space Quest
"No external C/C++ library dependencies" is simply impossible. Given that the host OS is not implemented in Python, some kind of bridge to its native libraries is necessary for a GUI library. Such libraries can be either compiled during the pip installation, or required as an external dependency installed using the package manager of the OS, Either way it's never going to be hassle free due to all the different OSes and package managers.
Your first point is true, but it's not the only explanation for why people still work 40 hours a week. My explanation is far more influential.

And your second point is blatantly false. That's the same, tired, rhetoric Republicans have been spewing since Reagan. Owners of companies doing well won't reinvest that into their companies unless there is demand on the consumer side and they don't spend all of that money on consumables like a worker would (since they have to).
I'd suggest that since the .NET hiring pool is vast, then you see lots of programmers of every quality? It could be sampling bias.
The good news is that pregnancy is almost an embarrassingly parallel problem. This gets reflected in polygynous societies and the occasional episode of Sliders.

http://sliders.wikia.com/wiki/Love_Gods
> is it actually the case that one woman can have a baby in nine months?

Yes, it is.

If your blog post's title is obviously false, you're doing yourself a disservice.
Do friends ever come up with good matches? Has this ever happened?

Still, interesting. +1 nevertheless.
I had a bit of trouble with that as well (I'm a class D player) but if you're still struggling the next move is Nxe6.
> is that the success probabilities of pregnancies are more or less independent

Or rather, if they demonstrate dependence, there's probably a factor outside of the pregnancy that's causing the problem (environmental stressors, toxins, etc.)
To be fair, the leading car companies have been working on electric cars for decades, as well. And Tesla just comes in and takes the lead (same for space launches).

Company age has nothing to do with its ability to innovate (if anything, you'd want to squeeze the last penny out of your existing tech/products before offering something new).
>You have to ask yourself, what is more important to your average impoverished american? a 50-100 dollar a month difference in family food/medical expenses, or a tenuous, debatable 0.2-1 point IQ difference out of an atlantic article talking about a single study?

Now, assuming for a moment that the study is right, and that this is focused on a small subset of the population and thus we are talking a one-point drop,[1] as far as outcomes on an individual's life go, you have diminishing marginal returns on IQ.[2] The point here being that a small increase in intelligence is going to help someone that is significantly below average much more than it is going to help someone that is already significantly above average, when you measure outcomes in things like income.

[1]I think speaking of IQ say, in deviation from the mean or percentile or something like that gives you a better handle on what's going on than "IQ points" though I read now that the two are convertible.

[2]http://web.archive.org/web/20060521185816/http://www.america...
> Fluoride is a perfect example: too little and your bones are weak

As far as I know there is zero biological requirement for fluoride. Fluoride can help mask systemic problems like mineral deficiency that lead to tooth decay, but nobody has ever had a cavity due to fluoride deficiency.
Or by Wikipedia: 25.4 millimetres
Talks and Reports
Ah, yes, another reminder of the hilariously bad user-agent situation in today's web...
You want to increase your IQ a point, do crossword puzzles.
The 20 Deadliest Events in Human History
Mono is about 25 to 50% slower on computational stuff, which is negligible in almost any business application that has a multi-server topology.

We use C# for business logic (API). One of the first building blocks was to create an open framework for defining and running services that both compatible with .Net and Mono. We've been using that now for a quite a while. While VS is still our primary dev environment for the API, Xamarin Studio is becoming more and more appealing. One of the obstacles when developing with mono is that not all functionality is available or identical. It's of course always possible to contribute a fix or missing code, but sometimes it's just easier to work around it (once you know where the hole is). In production, everything runs on Linux and we use vagrant provisioned VMs to replicate the latest release locally. It works quite well for us now, but it took some effort.

That said, we chose this setup because we liked C#, not because we wanted WCF or ASP.Net. We actually don't like most of the heavy frameworks, including ORMs. Instead, use rely on HttpListener for web-services, PHP for HTML page composition in-front of the API and straight-up MySQL queries for all DB-related stuff. It makes it much easier to evolve a running system when you know what the bits do all the way down! Just my $0.02 cents.
Same argument for shoes? Nobody ever hurt their foot because of shoe deficiency; it was the thorn that did it.

I think its disingenuous to ignore the obvious benefits of hardening enamel, regardless of other health issues in our population.
The problem of middlemen is a large part of why I am involved in a food coop. Our coop buys mostly from local farmers, and if you have any questions about how something was grown, they provide contact information for the farmers. I've spoken to the people who grow my onions and mushrooms in person.
Most tricky/useful commands for gdb debugger
Com'on Windows Phone!
My first thought when I saw this was to wonder how it might stack up to RESTangular, which I've toyed around with, but never really committed to because it didn't offer a ton of value over the in-built services and, really, just manipulating $http directly.

This, however, looks really solid, and excels in its very natural syntax. The way in which an object is called, manipulated and saved back is exactly how I expect an 'ORM' to work... at least until I get down to the "belongsTo" stuff, which is very Railsy -- that's fine, and the intro professes its attempt to mimic ActiveRecord, so it's even expected, just a little rough for me, as I left Rails for Django mostly because I preferred Django's ORM to Rails' ActiveRecord.

Regardless, I'll give it a shot.

In my skimming, I didn't see what versions of Angular it supports. I know that 1.2x has issues with PATCH operations (easily solved), and this didn't have any caveats for $.save() -- is it intended for 1.3+, or could I expect it to work on a 1.2x project?
Comments written in this tone have the fun property of being even more toxic when they're correct, which I'll stipulate that you are. They have a high valence, because people recognize and relate to the underlying correct argument even though it's hidden behind a cloud of snark. The force they exert realigns the thread towards meanness.

And, obviously, they're embarrassing for the correct side of the debate, which has been caricatured.

Please, please don't write like this here.
HTML5 DRM (EME) only defines an interface between the DRM system and the browser, it doesn't specify the mechanism for the DRM itself, the CDM is a black box . You could have a DRM scheme based on ROT13 and it would be entirely valid.

https://dvcs.w3.org/hg/html-media/raw-file/tip/encrypted-med...
If anyone gets it working, my start-up is doing some interesting things with Netfix: turboflix.com
SQLzoo.net has quite a bit of lessons. It has both interactive practice sections and multiple choice questions at the end of each lesson. I found that it wasn't well organized though, the path you follow wasn't obvious.
I think the main message that independently working on the same task can be a weak parallelization of random time tasks (independently random depending who is working on it). It simply falls in the category of "less than linear speed-up" parallelization. Since it is a trivial one, you can take it into account most of the time, however it's not too efficient.
The bad spammers are using botnets. This would be extremely difficult to implement and would mostly hurt mailing lists.
I like how the misconception is introduced by the standard library itself misnaming its own method `sequence`.
I'm a legal assistant for a mid-size law firm that mostly caters to other small- and medium-sized businesses. I basically just enjoy the topics discussed here.
B2B versus B2C (follow the money).

Games are cheap consumables, and with phones and other consumer devices, for example, you even have a cottage industry based around ripping devices apart and itemizing costs down to the pennies, analyzing how much companies are profiting from each sale, etc. (And I'd guess that commercial devices are more profitable, but a much smaller hiring market.)

Business customers--for the most part--just sign on the dotted line for products and services.

There are of course consumer-focused Web companies, but I'd suggest that venture capital (necessarily) covers salaries for most of these.
I'd also be very interested in this question. As a zsh user, I'm always eyeing fish, which seems to be getting better all the time.

I'm also interested in making bash tab completion behave a close as possible to zsh, just for those servers where installing zsh is a hassle. Never found a way. It's always slightly different, and thus very annoying.
Meet the anonymous app police
No, that's not what he meant. He was referring to the x86 microarchitectural side channel trend that started in 2005, with stuff like Aciicmez's BTB timing paper, or Osvik and Tromer's local cache timing.
>You want to increase your IQ a point, do crossword puzzles.

Do you have a reference for that?

In my own experience, my test scores have not significantly changed over the last 23 years.

Now, I'm not claiming that any test is perfect... but from what I have experienced and what I read, they do measure something that does not change all that much after you reach the age of reason.
As a Python library, the package would be called python-toga.
What do you use for temperature?
State is sequential when it matters

x <- get
put y
z <- get