skysight-inc/HackerNews huggingface dataset:
LTE-M is a game changer for IoT
I would say that Obamacare is a problem, in several ways:

1. It's important to note that people buying insurance for themselves is a small minority of the market (employer-provided and medicare/medicaid are the big parts of the pie), so it's absurd for the architects of Obamacare or any alternative health law to penalize (edit: or threaten to penalize, without conferring coverage in exchange for the penalty... no can do, that would be the evil public option!) the exact people they need to help the most: people whose employment doesn't provide insurance, and who don't qualify for medicare/medicaid.

If you're in a large health insurance pool with people negotiating for better coverage and pricing on your behalf, and the org behind the pool is already committed to paying the pool's insurance costs, things work pretty well. That's not a healthy private health insurance market; that's an opaque, balkanized system.

2. The (increased) number of insured is commonly cited by proponents of Obamacare as the metric demonstrating success. The numbers I've seen, however, show that while yes, more people have insurance, fewer people can actually pay their medical bills if they actually have to use their insurance. I have every reason to believe that's true, due to opaque pricing, massive deductibles for most plans, and the rapidly ballooning price of even the most basic plans. How is more coverage a success when most of those newly covered people can't pay their bills?

3. The obvious: healthcare insurance costs are skyrocketing. Obamacare can't be a success if just the cost of health insurance is going to start pushing massive numbers of lower-income people out of the marketplace.

1a. A tangent from point 1: The tie between employers and health insurance must die. There's too much incentive to do things that are just awful when most larger corporations will just eat the cost of reasonably good health insurance, and tweak their business elsewhere (increase prices; decrease other employee benefits) to make up those health insurance expenses if they go up.
For what it’s worth, I’d probably be more interested if it was something I paid for. Otherwise, ends up looking a lot like the existing contingency recruiter model.
It sounds like Marine pilot flight-gear of the time didn’t include a reserve ‘chute. Is that right?
>>What do you need a clearance for?

I dont, it was a question on if my Anti-Government Libertarian Principles would disqualify me from getting one.

> It's a stressful thing to keep, it's a really heavy responsibility,

I am sure it is, I know I would not be able to cover up for constitutional abuses my ethics would not allow for this.
That's fine for functions that go cold, but what about additional containers that spin up when usage spikes? Don't those also suffer from cold start delays? I never hear people talk about that.
Anti-tech propaganda based on false premises and the public isn't buying it
I would say that if it has stop signs it's not a roundabout -- the concept requires that incoming traffic yields to traffic on the roundabout but need not stop.
> Anyone is perfectly capable of implementing a Maybe/Option/whatever type in C

1. No parametric polymorphism, but I'll let you move the goal post with us macro-ing a bunch of monomorphized nullable pointer types. It still sucks because

2. No static checks against nullable values in the non-Maybe case, no ergonomic pattern matching in the maybe-case

Moreover, let's be real. Nobody writes new C in a vacuum, and given that that ecosystem is very mature, there's no changing course now. But safety techniques are only as good as their weakest link---their use must be enforced everywhere. The damage is done and irreparable with C.
Why you should use Magit: a Git porcelain inside Emacs
Same! I replaced it with Manga, read a couple chapters in my downtime or during meals. You'd the surprised the depth of these, they are usually well written, basically an ongoing book.
Yes, definitely.

My problem with crooters is not what they are ostensibly supposed to do, so much as that most of them are hopelessly inept at it. Good ones are hard to find. Ones that know their technical shit almost impossible.
I'd say Haskell is the right language for mathematicians to learn programming. Purity and laziness make Haskell definitions almost indistinguishable from mathematical ones; that means that the functional part of "functional programming" will come easy and you can focus on the "programming" part instead.
Launching Luminoth, our open source computer vision toolkit
Well I did mention it's "an end-of-the-world type vulnerability, at least as far as Wi-Fi goes".

I don't think it's a lot of consolation saying something along the lines of "Wi-Fi security is broken, but it's not so bad because it's Wi-Fi"
Not sure if you're joking. So you sleep 10 hours a day?
Supreme Court to consider major digital privacy case on Microsoft email storage
Sure I do. And I often get it wrong because people are extremely unpredictable.

I'm coming up to an intersection and I see someone edging out, so I slow down and prepare to panic stop in case they pull out in front of me. They don't, so I proceed. That's good defensive driving, but a failed prediction.

I see someone with their signal on in the next lane, so I back up and give them some room to move over. Turns out they just forgot their signal was on. Again, good defensive driving, but an incorrect prediction.

People don't break the rules in anything like a consistently predictable manner. Not around here, anyway.
That did not make landfall as a hurricane.

"In south-east England, where the greatest damage occurred, gusts of 70 knots (130 km/h; 81 mph)" https://en.wikipedia.org/wiki/Great_Storm_of_1987

However, it takes Sustained winds of 111–129 mph to be a Category 3.

Also the great storm of 1987 made landfall significantly south of this one. http://engweb.swan.ac.uk/~hewstonr/Great_Storm.html vs. https://en.wikipedia.org/wiki/Hurricane_Ophelia_(2017)#/medi...
> Dogs have roughly the same visual capacity as humans

While I more or less agree with the rest of your post, source needed on the quoted part. From everything I’ve read on the topic, there is significant differences in dog perception over humans (FoV, depth perception, motion detection, flicker fusion, etc).
Having an entire product rest on your shoulders sucks and emotionally drains you rather quickly. In my case it was a startup with a technology I created on the side that became the main business and eventually became the sole earner for a company whose other business had already been dwindling.

At the time there were maybe half a dozen people in the country that even worked in this particular niche. If I left the company it would likely go down, and the CEO kept telling me how many people would lose work if I left. And the pressure and responsibility kept growing and growing. And the sales people, who made up half of the staff, kept getting more and more antagonistic, as I couldn't meet their constantly larger expectations, which were often technically impossible (like sci-fi movie level). This situation lasted for over a year, culminating in a huge blowout between the CEO and I when I left.

I became a Rick real fast. I still feel like shit for being a Rick, and it's taken years for me to move that experience out of my "work baggage".
It might be more of a question of field. Based on my hopelessly incomplete view from the outside, in cosmology and closely-related subjects, it's impossible to work independently and accomplish much of anything. You need observations from many different sources.
100% agree!

How would this work in practice? Naturally you would need a free/open/secure mobile app (maybe such an app exists already?). Is there a way to hold and transfer fractions of bitcoin without using exchanges? Can I purchase fractions of coin from exchanges and transfer those fractions into my personal wallet?
I'm guessing Ken Iverson's APL wouldn't work here? It can show algorithms just fine. I'm not sure about type theory though.
I bought mine on Amazon.de on 2017-03-02, and it was apparently sold by MTRIX GmbH. The replacement form tells me "Please contact the team or individual within your organization that issued your current YubiKey."

Yubico told me:

> Thank you for contacting Yubico Support. That was bought through MTRIX GmbH, one of our resellers. They are responsible for replacement of all devices bought through them as part of the reseller agreement. You will need to contact them for the replacement process.
Good question, it should be fairly straight forward to add support for multiple projects, one approach could be,

1) make projects to be monitored configurable in app.yaml

2) grant app engine service account permissions for BQ read/kill jobs API

3) provide a dropdown for selecting project

4) profit!

if there is enough interest, we can add this in.
On the Myth of the Chemical Imbalance – Psychology Today (2017)
Yes, AEB and Adaptive Cruise are the two most important features I looked for in a car. I ended up leasing an EV without them (waiting for my Model3), but my next vehicle will require these (for example, almost all Toyota models have similar features - TSS-P warns for frontal crash but doesn't brake immediately).
LIGO is a new telescope. Everyone is hoping that, like every other form of telescope ever built, it will 'see' things that we didn't know were out there. There are lists of unexplained phenomena that telescopes see very regularly. Trying to explain such observations is the forefront of astronomy and physics (see dark matter/energy). But this telescope has yet to add to the lists.

https://en.wikipedia.org/wiki/List_of_unsolved_problems_in_p...
It wasn't that ambiguous. A government employee can have anything from a civilian clearance to a top secret clearance with whatever additional riders necessary to get them access to the information on that project.

Useful information, a red herring to determining how unique or nefarious facebook is here.
It worked for me, but I guess (also based on comments here) it depends on personality. I like to learn (work things out) from theory and I generally prefer to learn elegant languages that introduced some concept rather than a watered down version of that concept as it was adopted in more pragmatic languages. Some other people might prefer to be more practical and understand the theory later, and so prefer languages that are more pragmatic before they accept a new paradigm.

Haskell, due to its annoying insistence on pure functions, made functional programming click for me. I have seen functional style in impure languages before (Common Lisp) but I didn't have the discipline to really code that way - I only saw the downsides. Haskell forced that discipline on me, so I could also see the upsides. One significant upside is that one is forced to make functions really small, which leads to more readable and composable code.
I'm guessing stablemap is providing the author for anyone who might be interested in more of their work, rather than as a criticism or correction. ¯\_(ツ)_/¯
That's not the attack at all. And there's nothing standard about it.

The attack is the fact that someone couldn't do this you're describing on any WPA-2 protected Wi-Fi network before, and now they can.
https://www.youtube.com/watch?v=xAoljeRJ3lU

here's a great talk about this, in the context of replacing the Jet colormap for matplotlib.
I switched to an iPhone SE recently and it seems to be the best of both worlds. Uber, GPS, and internet are there if I need them, but that tiny screen makes aimless browsing much less tempting.
> Yeah, that's not a great study (though it was admittedly pretty groundbreaking,) and it doesn't actually prove that there is no relation between speed and accidents. Multiple studies since the 60's have shown different results.

The link sourced multiple studies. The originals were dubious, subsequent ones not so much.

But the issue the Solomon curve and other similar studies points out is that humans (and largely Americans) will ignore the rules if they feel they can safely go faster.

And sure, you can't ignore overall average speed. Crashes on roads where the average speed is 100 mph are going to be much more prone to fatalities than 55 mph roads. So, there are two rough equations: Lower average speeds mean less severe crashes; speed limits set to the 85th percentile mean fewer crashes. As the speed limit is raised (from 0), there will be at least one solution that satisfies both of those equations and results in the fewest fatal crashes (if that's your goal).

In certain situations the lower speed limits can make things less safe. For example, a straight, well maintained toll road with wide lanes, clear vision ahead, and say wildlife barriers that was designed for 75mph max speeds is constructed in a state with statewide 55mph speed limits. Construction uses the latest traffic easing and safety techniques, since you don't want to construct all roads to enforce speed limits that may change in the future.

So now most truckers and cautious drivers go 55mph, while people with less inhibitions are weaving in and out of them.
> Driving at roughly the same speed as the rest of traffic is definitely much safer than driving the posted speed limit.

Who is causing the danger of driving the maximum legal speed.

Also, it's rare that all of the traffic flow is above the maximum legal speed. The ones speeding then cause the differential, which is the danger.

The fault is not with those not keeping up. But rather with those breaking the law because it's convenient.
Apple must have invested incredible resources on testing that internally, because that was a very risky move, and well outside the norm for filesystem development.
What can be attacked is the keys generated by the TPM chips. So things like biometric authentication and full disk encryption which rely on the TPM are vulnerable. Stuff like TPM based signature verification isn't directly affected unless the signing keys also were weak.
True, however I'd say this is a problem with having an incompetent person in charge, not a problem with the process. I've had the experience you describe but also the opposite experience where people understood the need to rework things and what the business impact of not doing it will be. What makes a difference are 2 things:

1. The person making a decision like "should we do refactoring" should not be incompetent. They should be technically great and also in tune with the company's business needs. I know some smaller companies have non-technical people in all non-dev roles, so it's either the devs who do the work deciding or a non-technical person deciding, but that is just stupidity, at the very least the guy who is the boss of the development team should be a development guy. I seriously doubt that at for example Microsoft or Google, a non-technical person makes this type of decision.

2. The incentive system should not be messed up. Especially at companies with multiple levels of traditional managers, you have problems like people treating their job almost like a game, where they try to make their numbers good at the end of the year or avoid ever telling their bosses something their bosses don't want to hear... They completely lose alignment with the company's interests and treat their job like a game of looking good to their boss, so even if they understand the need for something they might say no to avoid missing a deadline they told their boss they would hit etc... This doesn't really happen at SD companies because most of them are new and never developed this type of culture but it happens at companies that are in another field and just have a SD department

I also don't think the solution of "30% of time" is good. Sometimes you need more, sometimes less, sometimes it's more important, sometimes less, sometimes more urgent, sometimes less. I still think you should "sell" refactoring to your boss, but the "boss" at a level where "should we refactor" decisions are being made should be an extremely technical guy who also knows how it will affect the business side of the project.
Except that, in this case, project continued more successfully without Rick then it did with his unofficial leadership.
> US federal + state + local governments spend an obscene amount of money on healthcare. Including extra funding to keep many rural healthcare facilities open etc.

"Extra funding to keep rural healthcare facilities open" is exactly what I'm referring to.

Medicare rates are below what would be needed to sustain practices if they operated solely off of Medicare reimbursement rates. Medicare reimburses about 7% less than the costs of supplies, which means they're already losing money even before they have to pay things like staff wages, building maintenance, etc. The way they stay in business is by charging privately-insured patients much more, in order to cover the difference.

Some providers don't see a lot of privately-insured patients, and for those, Medicare provides two different payment programs (separate from normal reimbursements) in order to keep them in business. Otherwise, they would end up closing shop[0], because there's no way that they could sustain themselves off of Medicare reimbursement rates alone. For various reasons, this is more common in rural areas than it is in urban areas, though the program you're referring to does apply to some non-rural hospitals too.

So yes, when you say "Medicare pays extra funding to keep rural healthcare facilities open", you're actually referring to the exact reason that private insurers would love a transparent pricing system. It's not like Medicare pays this money to any rural facilities - they are forced to pay extra money to facilities that don't see enough privately-insured patients to cover the losses that they're making on Medicare patients. Private insurers (and providers) would love to have a transparent pricing system, because that would mean they wouldn't have to bend over backwards just to break even on their Medicare patients.

This isn't hypothetical; Medicare paying extra to these hospitals is a relatively new practice, and it was passed by Congress after a large number of hospitals were forced to close because they went bankrupt treating mostly or exclusively Medicare patients.

[0] Or just stop seeing Medicare patients, which is what many have done.
"is there any mitigation for this other than ditching my handset and switching to an iPhone or waiting (hopelessly) for a patch from my vendor."

Using a VPN is the best way to mitigate this until your device is patched, assuming you trust your VPN provider or run your own VPN.

Edit: Actually, even if you don't trust your VPN provider, you'll be protected against this attack (KRACK), given their client is implemented properly.
They are.

Try driving in Asia and get back to me.

(Disclaimer: I'm hard line traffic law follower.)
Companies mostly don't hire because there is that perfect talent/match out there. They hire when they need to. The current model works for the employer and recruiter because whenever there is a need, the company will create a job opening and the recruiter fills it in. Candidate doesn't pay anything out of their pocket.

The only way for an agent to work is for companies to be open to good talent and keep them on their radar even if there is no current job opening. This is usually difficult and not worth to companies. If you become an agent, you will also be at the mercy of asking the companies "hey do you have an opening yet, I have this great guy/gal". So that model fails.

Also, don't forget that there is that tiny population of good recruiters out there who are directly connected to employers and have a rolodex of candidates they have worked with in the past. They can match the candidate to jobs that fit them. Rare but out there. I know a few.

So yea, I don't like the status quo but I struggle to come up with an alternative yet.
> Not every employee “got it” right away, according to Bret Boulter, the Microsoft real estate and facilities manager who led the project. He was quoted on the company’s blog, saying, “A lot of people are like, ‘where’s the AV?’ And I’m like, it’s a treehouse.”

Gold.
Computers have been training humans for the past couple decades, and I see no reason for that to stop just because the computer's form factor is a car.
It has a shallow learning curve, if you use the term correctly. The graph of the amount that you have learned rises gradually over time.
Wikipedia doesn't present it as quite so selfish:

"By accepting a modest delay in going straight, the opposing traffic has saved the left-turning traffic waiting an entire light cycle to turn left, as well as saved an equivalent amount of time for all the cars that otherwise would have been stuck behind the left-turning car. In situations where there is so much oncoming, straight traffic that a left turn would not be otherwise possible during any part of the light cycle, the Pittsburgh left can allow a line of left turning traffic to proceed incrementally."

https://en.wikipedia.org/wiki/Pittsburgh_left
Ask HN: Survey – Would You Use a Recruiter? Yes/No
I'm very curious to whether other engineers would use a recruiter and understand the ratio. As you can see, I'm very passionate about this space and I've been asking the Hacker News Community a lot of questions to do research :)
It's not that simple. If the payers other than Medicare had more negotiating power relative to large provider organizations then they could also drive down prices. The providers have a lot of room to stay in business and trim fat by eliminating waste, reengineering processes, cutting staff compensation, and squeezing suppliers.
FTSite: ''Simple, straightforward, pricing. $1 for the first four pages, $0.25 for each additional page.''

Twilio charges are generally under $0.25/min for outbound phone calls in the U.S. and $0.01/page for programmable fax. If you choose not to opt for Twilio Fax API, lambda function to encode and send the fax is a fraction of a penny instead. So there's probably some room for profit margin either way.
IIRC this was a huge talking point during the 2008 election cycle via https://en.wikipedia.org/wiki/Pickens_Plan (the section on "Peak Gas" is particularly relevant).

I'm surprised that the article doesn't even mention this.
I like much more this one by the Science Magazine:

https://www.youtube.com/watch?v=e_uIOKfv710

and this one by The Georgia Institute of Technology:

https://www.youtube.com/watch?v=pLivjAoDrTg
Right, so the reward/risk isn't enough for you. It's also prudent to stop at a green and look both ways but nobody does this either.

At the end of the day you either trust other drivers or you don't. You're not exposing yourself to any significant addional risk by making these 'safe violations' than you do driving in general.
Is there any other language with purity, laziness, and static types that could possibly be put forward as an alternative to Haskell?
Functional programmers practice a form of no-true-Scotsmanism wherein type and category theory are an intrinsic part of "true" functional programming. So unless you are working in something with a type system at least as expressive as Haskell's, you are -- arguably -- not doing true functional programming. (Sorry, Schemers.)
Yes, the original game would have been written in 6502 assembly, and probably would have looked something like this. The label names and defines would have been different, since the ones in this file are the interpretation of the person who did the disassembly.
I really wouldn't want to program a car that obeys speed limits in 49 states, and in one state "record[s] evidence of conditions which could show that the speed was reasonable and prudent given the conditions"

From an implementation perspective that sounds like a lot of overhead just to let Californians drive fast.