skysight-inc/HackerNews huggingface dataset:
> Sounds like the old price of $13 was way too cheap. Given that its off patent and still no one else wants to make it I'd think the new $750 prices is probably not crazy.

On top of that, there was an investigative article a while back that tried to measure the actual effects on patients.

Turns out, they weren't able to find any patients who themselves had to pay anything close to $750/pill for the drug. It's not prescribed that commonly in the US, and the only patients who needed it were all on insurance plans that covered it, subject to standard copays and deductibles. Many of the patients already meet their annual maximum deductible anyway, due to the other medical care they already have to receive, so the marginal cost to them was $0. In other words, raising the price of the drug literally did not increase the price that those patients had to pay by one cent.

I'm aware that this has a complicated and implicit impact on prices elsewhere, but that's the real problem: medical billing is ridiculously convoluted, and focusing on the price of a single drug - especially the price that isn't actually paid by any consumer - is missing the real problem that needs to be fixed.
5 web design templates you need to have
You can imagine their disbelief. This almost certainly never crossed their minds. What kind of tank designer thinks about mouse protection? Nobody planned this, nobody expected it.

But these things happen all the time.

Risk does not like prophets. It’s not even fond of historians. You can plan for every risk except the things that are too crazy to cross your mind. And those crazy things do the most harm, because they happen more often than you think and you have no plan for how to deal with them.

Risk in most professions is managed by studying what’s common. Maybe 10 topics and their solutions, said slightly differently, dominate business and investing books.

The problem is that historical risks you can study are dwarfed by risks you actually experience. There are a zillion treacherous risks, but most on their own are not common enough to take seriously or collect data on. Like mice destroying tanks.

Search the New York Times’ archives, and you’ll find that the word “unprecedented” has been published once for about every ten instances of the word “common.” Which is a lot. Stanford professor Scott Sagan nailed this when he said, “Things that have never happened before happen all the time.”
The Ford F-150 is the biggest selling vehicle in the US. Ford haven't even tried to sell it in Europe, because there's no demand. They do sell the Ka, a model even smaller than the Fiesta that isn't available in the US.

Ten years ago, the market for grass-fed beef and organic vegetables was negligible. Consumer demand induced the agricultural industry to start shifting towards production techniques with a lower environmental impact.

Consumer demand matters.
Personally, I'd be fine with all that if not for the elephant in the room - the superlinearly growing, unbounded energy upkeep required to support cryptocurrencies. That one single reason alone outweights all the potential benefits you allude to.
Sure, but you could point a generic client at a SOAP endpoint, and have a client for it, since the endpoint told the client what methods were available and what their signatures were.

REST lost that.

I think GraphQL has it back again. Any GraphQL people want to comment?
Do you know if they need a solid business case even if it is optional? For example, any idea if an optional "locate your device" feature would get shot down?
I recently came across https://www.moo.do. Might be what you're after.
I think the more important divide between language communities may be between consensus and individual authority. Python's BDFL and Javascript's standardization lie at opposite ends of the spectrum. To caricaturize: Javascript is the intersection of what many interested parties can agree on. Python is the union of anything that struck a single individual's fancy over the course of decades. The rise and fall of functional programming as Pythonic is a case study of the language community's arbitrariness (if Python2 v Python3 wasn't enough). As an aside, Ruby avoids this because it's vision is not tribal. Principle of least surprise allows for differences among programmers. Pythonic/unPythonic doesn't.
Как стать экологом аудитором (инженер-эколог по экоаудиту)
He was convicted more as an example to other people who might be inclined to disrespect the courts as he did.
> Nice. How come no one can ship it across the pond and stock it then?

Because reimporting prescription drugs (manufactured in the US and sold abroad) is illegal. There was a bill that would have allowed this, but it was voted down in the Senate last January.

To be entirely honest, if that bill ever did pass, there would be serious pressure political pressure on European governments to ban re-exports of prescription drugs from the EU. The current barrier to trade is what enables European governments to set low prices for prescriptions while still maintaining the same level of profits for European pharmaceutical companies - the latter simply raise their prices in the US to make up the difference.
Your view seems to be to throw out the baby with the bathwater. The crypto space is full of scams, PnDs, etc. The crypto space is also full of world-changing technologies that will affect our economies and societies significantly. Both are true, and you'll be remiss to ignore that part.
do not parse the output of ls

http://mywiki.wooledge.org/ParsingLs
Or it's not worth spinning up another line for 50% of a small market. There's huge NRE costs to making that happen.

When we're literally talking about medicine, I don't have a lot of patience for increasing costs to 'what the market will bear'. There's obvious market failures occurring.
This is actually Central Park theory from The Killing Star.
DollarStreet link: https://www.gapminder.org/dollar-street/matrix
Chamath Palihapitiya: I'm a Buffett 'disciple' but he's wrong about Bitcoin
Yes. Exactly.

That's why more and more people getting involved in scams and get-rich-schemes on a platform with superlinear and unbounded energy upkeep is something that worries me deeply. Energy and climate is something that very well may break our society.
Ask HN: Is there ANY way to delete my Dropbox account?
.
Cokeinoes: Cocaine delivered faster than pizza
Does anyone use Taskwarrior with more than just a few tasks? I have about 15 projects going at once and flip between them numerous times during the day. The projects might have several sub-projects and multiple next actions.

Are Projects/Subtasks implemented well?
When I first learned about computer networking, I remember being blown away when I learned that network congestion dynamics also explained how freeway traffic worked. It’s cool to see the same idea in this article!

Specifically, I thought it was amazing how it explained why if someone stops abruptly on a crowded highway, every subsequent driver will have to experience that pause, even hours later, so long as the highway maintains the same level of congestion.

You network folk will undoubtedly explain it better than me, but I think that's the correct gist of the idea?
What, is it legitimate companies selling your data?
The fear media told me it was hackers.
Stewart Brand: The Man Who Changed the World, Twice
[ ] has a way to test data connections before trying to use them

[ ] has a clean way to do releases

[ ] can handle more complex network setups (like found in docker envs)
Ours went haywire and crashed into a pond onetime when we used the Return to Home feature. YMMV
OpenBSD uses vnconfig (also FreeBSD; on NetBSD it's vndconfig). An example:

# vnconfig vnd0 install63.fs

Then you can treat vnd0 as if it was a disk:

# disklabel vnd0
# /dev/rvnd0c:
type: vnd
disk: vnd device
label: fictitious
duid: 138b4f2a2e184426
flags:
bytes/sector: 512
sectors/track: 100
tracks/cylinder: 1
sectors/cylinder: 100
cylinders: 7382
total sectors: 738240
boundstart: 1024
boundend: 737280
drivedata: 0

16 partitions:
# size offset fstype [fsize bsize cpg]
a: 736256 1024 4.2BSD 2048 16384 16142
c: 738240 0 unused
i: 960 64 MSDOS

For instance, to mount the 'a' partition:

# mount /dev/vnd0a /mnt

You can also associate an encryption key with the device. All data written to the diskimage will then be encrypted.
Why wouldn't they just store it in a Swiss bank box or something?

Can the wealthy not just use their art/gems/gold storage choice. Do hardware wallets need power?
A big part of the problem IMO is the software development community has gravitated toward rate compensation instead of product compensation. A composer is commissioned to deliver a product and is compensated for said product, not for the time he/she worked to create the product.

This was real eye opening for me when I did contract/consultant work, even as a 1099. I can understand the enterprise, butts in the seat model of developers being on retainer but for contracting houses I don't get it.

If developers don't want to be bound by these metrics they need to get better at forcing the client into contracts for deliverables with clearly defined acceptance criteria. Also, it seems to me that the best way to get proficient and creating and updating these contracts is by having to work twice as long to deliver a work product as was initially estimated.
Generally the workflow framework ought to be doing very little compared to the jobs it orchestrates and executes. In the common use cases, airflow is often only a little more than an (distributed) executor/scheduler for bash commands.

Wouldn't the value of optimization at the framework level, be generally... very little?
Why is a todo list a good idea?
Outlook/OneNote combo works well for this.
Don’t kno about Mac but: https://www.google.com/search?q=outlook+task+from+email&ie=U...
Very much this.

It may be worthwhile for really complex and "business vice separated" services to be written as micro services because it gives you clear separation of concerns. But, in reality, to often you see a single logical service getting implemented with a lot of (N/W + serialization + management) costs unnecessarily just because it is cool to say that you did micro services.

My thumb rule is : If you don't foresee different teams of devs working on these different services, then you're better off leaving it as a monolith and scaling it as a whole application instead.
This is one of the standard PhD-level textbooks. It's probably a little bit much if you just want to use somebody else's library, but if you're developing your own algorithms or you want to engage seriously with the research literature, you have to know what's in here.

The main other books I'd consider are Foundations of Machine Learning (Rostamizadeh, Talwalkar & Mohri) and Machine Learning: A Probabilistic Perspective (Murphy). There are a few others, but I think you'd need a good reason not to pick one of those three.
What if your service requires the tracking?
What? In what world is QE 1,2, and 3, the dramatic and unprecedented expansion of the ECB's balance sheet, and the BOJ and SNB openly buying equities "focused on eliminating inflation"?
> the system depends on extremely sophisticated infrastructure that was built and enabled by governments.

... and which continued existence and operation requires stable governments keeping most of the planet bound by the rule of law.
Assuming you're not one unlucky enough to need it, sure, it makes perfect sense.

<blunt>

But if you're unlucky enough to have a baby that gets toxoplasmosis, you're fucked. The people backing the insurance which is paying that new price are fucked. But it's OK that this is a net negative for society, because the company is now making a 'proper' amount profit off it, right?

</blunt>
This being Hacker News, we can talk about it in terms of graphs, right? Let's look at the sociogram when one parent is present.

The transition from zero to one is of course world-changing. But at one child, 100% of the connections in the sociogram connect to a given parent: zero economy of scale.

At two children they have each other, but that is only 1/3 of the children's connections when one parent is present.

At three, we're up to 50% of the connections that are child-to-child. At this point the sociogram is rich enough to become interesting.

Four => 60%. Eight => 77.8%.
Suppressing hyperactive B-cell activity--which causes IBD--as well as scalp psoriasis why I eat a little rendered stabilized thymus 5x-6x/week: https://www.amazon.com/Standard-Process-Supplement-Supports-...
But they are still paying it, it's just obfuscated.

Since the ACA capped profit percentages, the insurance companies have been looking for ways to increase pay outs, os they can increase total revenue, and then total profit. That perverse incentive is one of the reasons why insurance premiums have been going up so much the past few years.
It really depends on what you need. I'll send you an e-mail.
The crucial information is up and down ticks of the ES-mini futures at the Chicago Mercantile Exchange. These lead the S&P500 (SPY) index funding in NYC (by 4 milliseconds), and the ES-mini ticks up and down about once per second. This few bits of information carries huge value since much of the world's equity market responds to it. See https://arxiv.org/abs/1302.5966
The key to getting a retainer irrespective of being a programmer, designer, or gardener is client selection. For a designer, one obvious route to passive income is licensing fees. But again, finding clients that will be happy to pay such fees is the bigger problem in a world where many people will assume they own the designer's design by virtue of commissioning the work.

Good luck.
Re the cult thing: I read an eye-opening paragraph about it somewhere. Basically, yeah, if you've invested in it, you have to either fool everyone else to buying into your cult, so the price will rise and future-you can cash-out and make a profit, or more likely, you're trying to convince yourself that past-you wasn't an idiot that just burned a lot of money. Or worse, you've convinced yourself that the USD will turn to toilet paper, soon, soon!

It's applying the formula of the shit book "The Secret" ("if you want it really hard, the universe will give it to you") to getting rich...
Your claim is revisionist and, in my view, nonsense. Scheme is most certainly a Lisp. I mean, you can think what you like, and of course postmodernism is a thing, "the author is dead" and so forth, but if you look at the history, it's very, very clear that Scheme is a Lisp; that is, it is a member of the Lisp language family.

You can even read the words of the people who invented and developed the language:

"SCHEME is essentially a full-funarg LISP." - page 1, "Scheme, an interpreter for extended lambda calculus", Sussman and Steele, Dec 1975. AI memo #349.

"SCHEME is a dialect of LISP." - abstract, "The Revised Report on SCHEME, a Dialect of LISP", Steele and Sussman, Jan 1978. AI memo #452.

"Scheme is a statically scoped and properly tail-recursive dialect of the Lisp programming language [...] Scheme differs from Common Lisp in its emphasis upon simplicity and function over compatibility with older dialects of Lisp." - page 4, "The Revised Revised Report on Scheme, or An UnCommon Lisp", Rees and Clinger (eds.), Aug 1985. AI memo #848.

"Scheme has influenced the evolution of Lisp. [...] Scheme was the first major dialect of Lisp to [do many things]" - introduction, "Revised^3 Report on the Algorithmic Language Scheme", Rees and Clinger (eds.), Dec 1986. ACM SIGPLAN Notices 21(12).

"Scheme is a statically scoped and properly tail-recursive dialect of the Lisp programming language" - summary of the R4RS, the R5RS, the R6RS and even the bloody R7RS.

Compare and contrast to the opening words of the Introduction to CLtL2, which are "Common Lisp is a new dialect of Lisp, a successor to MacLisp, influenced strongly by Zetalisp and to some extent by Scheme and Interlisp."

If Scheme is "not a Lisp", then neither is Common Lisp.
Outdated website software lets hackers mine cryptocurrencies at your expense
Looks coherent, informative and not too indulged with proving things with mathematical formulas. Problem is that the only way I could study it with the meticulousness it requires would be during a course. Studying it at my own leisure is a bit too much of a burden.

However what irks me a little, as it did with my university's introductory machine learning course, is the direct jump to the algorithms while omitting explaining the basis for the underlying cause why it is the right thing to do. Perhaps it's presumed that the reader knows the basic statistics behind the idea that we can make assumptions of the data and predict values due to central limit theorem. Machine learning itself then can be seen as a derivate of that as more free-form, heuristic approach to cases where the central limit theorem can't be applied or is too restrictive.

Am I speaking complete nonsense here? Please those wiser than me, tell me am I right?
Well to be fair the saying doesn't specify the state of the eels.

It could be liquefied remains of eels! Although I'm guessing we would need to study a few of the translations in languages that explicitly differentiate between "a collection of whole somethings" and "an amount of something". Although now that I'm thinking about it in english saying "my hovercraft is full of eel" would imply that it's an amount of eel, not a distinct number of eels.

Still, if it were the "amount", a simpler JS expression would convey the message:

const amountOfEelsInHovercraft = Number.MAX_VALUE
if this had a scheduler and an alerting mechanism when SLAs are breached, that would be great!
maybe future features?
The negative feedback loop on faulty signals should be a read for anyone doing engineering, including software engineering.

If the workers go the proper speed, the faulty signal will trip an emergency break. This actually threatens their jobs because they'll be blamed for tripping the e-brake as if the signals worked perfectly.

1. The management trusts the automation too much without proper checks or tests proving the automation is accurate.
2. These workers are still blamed, even after signals are known to be bad.
3. People, even in here, blame the workers (and the union) for the fault of the system's quality being garbage.
4. Workers try to preserve their jobs by just working around the problem and reducing productivity all-around.
I'm in the process of writing a book for this exact scenario. If anyone has suggestions for what topics it should cover I'd love to hear them!
So, one project I've been working on in the background for the past few years is a NIAC (NASA innovative advanced concepts program) proposal for using gravitational assists between a pair of planets to harvest energy from planetary motion by transferring momentum from the inner planet to the outer one. The harvested energy could be used to accelerate more mass into the loop and exponentially increase the coupling. In theory, this could move Mars into an Earth-like orbit over the course of a century while harvesting millions of yottajoules of usable energy. I call the proposal "Moving planets for fun and profit".

If you know anyone who is into orbital mechanics, I could use a collaborator. I have to spend most of my time on slightly less far-out projects.
I've been developing so-called "REST" services for over ten years (and SOAP services before that), and not even once were REST principles actually applied in the projects I worked on. As in, the client/browser discovers from an URL the interactions with a resource without out-of-band info for minimal coupling of client and service. I agree though getting SOAP/XML right takes typically considerably more effort than JSON.

Re: statefulness ("order matters"): there are intrinsical stateful processes that aren't represented adequately by a REST service. Think of a basic "Purchase Order" resource representing purchased items on an e-commerce website. You generally can't add and delete line items freely once you have placed your order, but you may cancel individual items (unless they're already physically on your way), you may RMA items, etc. Representing this as a flat "Purchase Order" resource with GET, POST, DELETE, PUT primitives is useless as it isn't telling your web shop front-end developers what actions are available at any one time.
Can you link to that article?
APIs map to a single canonical concept. A "class" in Java actually has a correct definition. There are a nontrivial number of philosophers who believe that this isn't true for language.

To simplify that and put it in more technical terms, an API is perscriptive and a language is descriptive.

If a bunch of coders decide to start capitalizing "Class" their code won't compile. If enough people start using the word "aint" it becomes a word, regardless of what the dictionary says (see "irregardless"). There is no single authority that can decide what is and isn't a canonical definition.

This is why spoken languages evolve so much. Even languages where we've explicitly tried to go the opposite direction (like Esperanto) have evolved into multiple dialects, where subsets of the community simply ignore the standards and still communicate with each other just fine.

Note that this is the opposite of what you want with a federated, universal API. The whole point of an API is to standardize between unfamiliar devices. Language is actually pretty bad at standardizing communication between unfamiliar people. Even in the US, different regions and communities use different euphemisms, terms, and definitions.
oh, that explains why nigerian scams dont work.

/s
python in airflow is just used to define your graph and trigger your jobs. I think it's a wonderful language to do this.

You can (and should) program your batch jobs in other languages than python if you have large amount of data of course.
It takes two weeks to reset the hash rate, if the hash rate stays constant. If it starts dropping, the time goes up.
Netflix Research
I admit to only having listened to one episode at the time of posting, it wouldn't surprise me. Stuff coming out of the intercept does appear to have a slant.
I'm one of a whole bunch of reviewers for Black Hat USA, which is the largest vulnerability research conference in the industry. For the past several years, if you were to submit a universal WAF bypass talk, enabling you to evade detection by every WAF on the market for every common attack, there is a really good chance that talk would not be accepted --- too boring. Almost certainly a WAF bypass that evaded all detection by a single WAF vendor wouldn't make the cut.

So, no, not really interested in generic SQL detection rules in WAFs.
Call your local representative and demand this then. That is how legislation is enacted.
CYA is rule #1 in bureaucracies. If something happens and you "do nothing," you're responsible, so you have to "do something."
What’s interesting is seeing SOA evolve: first it was service calls everywhere, now it’s increasingly asynchronous publish/subscribe architectures (think AWS SNS and SQS) and service orchestration frameworks (SWF, Step Functions). In my department we realized that 700+ services is untenable and we are now exploring home grown frameworks and SDKs to help manage those levels of complexity.
> But they are still paying it, it's just obfuscated.

They're not still paying it. Collectively, yes, the insurers are passing the cost on to the insured population. But the number of people taking that drug is tiny[0], so it amortizes very quickly. For the patients taking the drug, the effect on their own premiums from that price increase is less than a penny.

This is what I'm talking about when I say that medical billing is the real problem: the effects are non-obvious and highly-interconnected. You're right about the perverse incentive created by the MLR; and that's just the tip of the iceberg.

[0] There were 500 pills sold in Dec 2015.