skysight-inc/HackerNews huggingface dataset:
>But critics say that having too many emergency departments in one community reduces the quality of care because it shrinks the amount of practice that local trauma-trained physicians get when treating complicated injuries. A similar argument was made when Northside Hospital tried to open a trauma center earlier this year, but withdrew after two other area hospitals with trauma centers contested the expansion.

A spin on the Roemer Effect it seems. Florida apparently has a Certificate of Need policy.
https://gnunn1.github.io/tilix-web/ is a good tiling terminal emulator/terminator alternative if you're looking for something designed for GNOME 3
#!plumbum

https://plumbum.readthedocs.io/en/latest/
You live on the edge... I am on a legit mac and I'm still on HS for at least another month or two just to be safe.
Look Up Gleaming Geminid Meteor Shower of 2018 Peaks Tonight
I tend to view "science" as quintessentially a "success term." We call a discipline a science if we have a high degree of confidence in its results. In this sense, math is a science, and whether psychology or economics are scientific has less to do with their subject matter than whether we think they produce real knowledge.

I like this notion of science because it helps to account for the broader sense of "science" you see in earlier periods of history, before it became more narrowly associated with experimental science. More importantly, I think it gets at what actually interests us in the designation of "science."
Particularly exciting given that concrete makes up close to 5% of global CO2 emissions.
I've done a number of projects in both "waterfall"[0] and Agile.

On the "waterfall" projects, we wrote lots of documentation. LOTS. Business cases for every major feature. Requirements documents with serial numbered acceptance criteria. Design documents explaining exactly how we were going to implement the requirements, with every REQ bullet needing to be accounted for explicitly. Test plans showing how each DES bullet was implemented correctly and how it proved the REQ was satisfied. And it all had to be correct and fresh. We weren't allowed to have anything disagree or slip in or drop out. If it wasn't in the REQs, it didn't go into the software.

That meant if we discovered constraints that necessitated a change in design, we had to change the requirements. If you had to change requirements, it meant you had to reevaluate the business case.

And that meant we were prototyping while we were writing the documentation. The documentation wasn't done until the software was about 80% complete. By that time, we were mostly just working the test plans and resolving defect tickets to get to 100%.

Some of the best, longest lasting software I've ever written.

All of the "Agile" projects I've been on are what I call BTSOOP development: "By The Seat Of Our Pants". There was no attention paid to documentation at all. It was hell getting PMs to write any tickets, let alone ones that were in scope. And of the tickets that were there, most of the devs ignored them, even if the PM didn't. Some people would mark tickets done that they just didn't want to do, hoping the PM would just blanket-accept tickets at the end of the Sprint. Which he most frequently did.

The difference wasn't actually process. It was accountability for failing to adhere to the designated process. The Agile shops all had corporate policy on how projects would be ran, and nobody was ever taken to task for it. The "waterfall" shops didn't lack continuous integration and improvement or responsiveness to change, we just wouldn't sign off on a particular document until we knew it represented the final product, with linear dependencies on when different levels of assets could be approved (not when they could be worked on).

[0] our product manager called it "the NASA way", and we fairly closely followed their documentation standards, if not their engineering ones, but we were all pretty junior at the time. IDK why I was made senior other than being the best programmer there, which at the time wasn't saying much.
What do you mean "read"? Implemented.

Though obviously not the full thing. Nobody does that. Not even Adobe does that.
"Jeff, it's much easier to pave the way for Cthulhu when you pretend to be kind. Still a shitty thing to do, but easier."
How Does Angel Investing Differ from Venture Capital?
Earlier today, I took a note to myself saying this:

The next-generation development environment will be a combination of:

* a wiki (outlining content + version control),

* a spreadsheet (functional reactive coding + lightweight schema definition + easy working on collections), and

* a mockup wireframe builder (visual layout + visual state machines + rapid prototyping).

Pluggable connectors to constraint solvers and machine learning would be a plus.

I'm not sure that Jupyter fully captures all parts of the computation graph; most of all, restoring a previous state after closing and reopening it is cumbersome (if I'm not mistaken you need to run each individual cell by hand in the right order). There are theoretical models that could fix that, though, like those allowing for time travel debugging. And the visuals are simple and flexible enough to support many use cases. So yes, web notebooks are a good basis for a knowledge-building programmable platform.
Close but no. They add a five story wood structure on top of one story of something more solid like concrete. This cost effectively increases space without massively increasing costs over a five story wooden structure.
I can't agree that drug regulation hasn't increased safety. Safety incidents are still quite common with unregulated "supplements". See https://en.m.wikipedia.org/wiki/Zicam and https://www.nature.com/articles/ajg2014131 .

That being said, clearly the current system has flaws. Perhaps the FDA could alter their requirements for sale to approximate "does not cause harm", with additional classes for "provides more benefit than harm", etc. The problem is, how do you get drug companies to pay for effectiveness studies if they don't have to? This would actually disincentivize such studies.
> If we were chatting face to face would you also behave like this?

Maybe? I usually very much would not, of course, but JS "culture" creates significant irritation and wasted time for me daily, and has for years, especially in React-land, since that's where the money is lately so it's hard to avoid. The only other software that gets me this exasperated is anything Poettering thinks up, but at least I don't personally have to work closely with any of that daily (any more, and for now).

I'm sure I'll have to deal with hooks when people around me start using them. It's less that I'm upset that they exist than I feel like I'm being gaslighted. I've read the docs, and the source, because, again, I have to know this stuff. After the initial disbelief wore off I had a good laugh, like, actual LOL. This thread is the first of many I at that moment predicted I'd see as people who really, really in their hearts and in their actual technical needs and in the language they're using, just needed OOP, but are on the JS-must-be-functional-at-all-costs hype train, expressing frustration and confusion over this feature and burning lots of time trying to sort out how OOP works when you're trying so hard to not type "this" and pretending it's something else. It's a less-useful and confusing replacement for OO that re-implements just enough of it that people will 100% for sure hang themselves with it, and omits enough that people will complain about it. It's a perfect device for generating confusion. It's going to be used for no benefit, or misused harmfully, a ton, and meanwhile everyone's gonna be very confused about it.

Ditto Redux—which is at least not funny in itself the way React Hooks are, though the flailing and consternation around it are—which is dead simple if you don't use the wrong words to describe things, yet how many person-hours have been lost trying to decipher what's going on there? So, so many. On the one hand it's funny, and I do legitimately enjoy all the accidental humor in React land. On the other I have to console, counsel, and train the folks who run into difficulty with this stuff, and live with or fix software in which it's been misunderstood and misused.
MS' Matt Torgeson explained that once. Their investment is aligned with the user base. There are millions C# devs, 100 Thousands of VB.NET devs and 10 Thousands F# devs. But in difference to VB, F# has a independent community with a strong focus on improving F#.

All I hear from MS is that they love F# but the workhorse is C#.
Well, you can:

* Push your politicians to support GDPR-style legislation

* Donate to your politicians so they actually listen

* Run for office

* Try some weird tech solution like dazzle clothing (this won't work most likely)

* Take inspiration from Exit, Voice, and Loyalty, and emigrate to a place with governance that more closely reflects your own values. A place covered by the GDPR would be a good start. _Presumably_ if your country loses enough talented people it will work to retain them. But, that's a pretty long-term approach and I have doubts about it's true efficacy (My homeland is hardly building great bike infrastructure since I left, and that was one of the biggest motivations)

* (Also pretty extreme and of dubious efficacy long-term) live off-grid somewhere remote and not walk by people's houses.

Probably a lost cause, though. I find it infuriating that my voice is being listened to by Alexa, etc. when I'm in other people's homes, but they don't seem to care. Maybe civilization will collapse and render this a moot point.
You're preaching to choir. I think they are beautiful cars, but for other people. I've never paid over 10k for a vehicle, and I've never paid a mechanic. I only see a vehicle as a tool and Tesla is just another impractical status symbol but I absolutely admire the technology
omitted from the title, but included in the article, is that they're also expanding in boulder colorado.

i know that location has been under construction for at least 6 months now. my business was having some construction done, and we kept getting bottom of the barrel subcontractors, because our contractor also has the apple building, and kept sending their good folks over there. :(
Somebody better tell Ireland...
I got this creepy recruiting email from Amazon.

"Amazon PeopleTech’s mission is to re-invent ways for our employees to connect with one another. You will work closely with our team of engineers in designing a strategy for new projects like our new Facial Recognition technology for Amazon’s Time and Attendance systems"

I love connecting with people!
Accessibility, plus print is at ridiculous DPI compared to screen. To achieve compression you want to use the fact that there is a font being repeated across the page. OCR just isn't good enough.
Have you written about this anywhere (or can you point me toward someone who has)? I've had teas made from myriad wild/edible plants in the Pacific Northwest, and am always interested in learning more about others' experiments.
My list has a lot more fiction than others here, but I enjoyed myself!

Just For Fun - Linus Torvalds (Highly recommended, Tells of Linus's early life and how Linux came to be. I'm surprised I haven't seen this recommended more often.)
Into The Plex - Steven Levy (The history of Google, definitely worthwhile)
Dune - Frank Herbert (I enjoyed it, but not enough to pursue his other books)
The Color of Magic - Terry Pratchett (Kinda interesting, but rather odd)
Last Kingdom, The Pale Horseman, Lords of The North - Bernard Cornwell (The first three books in his Saxon series. These are what The Last Kingdom TV series is based on. Worth a read if you liked the show or like English history.)
REAMDE - Niel Stephenson (Very fun! Lots of crazy action while still being almost believable)
Seven Eves - Niel Stephenson (Typical Stephenson Sci-Fi. Very interesting take on an Armageddon type scenario)
The Hardware Hacker - Andrew Huang (Talks a lot about manufacturing tech in China. Neat to see some of the processes behind the devices we use every day. Also interesting if you like the idea of open hardware.)
The Art of Wheel Building - Jobst Brandt (I've built a few bicycle wheels so this was interesting to me.)
One of my favorite short stories is Youth by Joseph Conrad, which has as a central event a ship sinking because of a coal fire...

https://www.gutenberg.org/files/525/525-h/525-h.htm
The usual body-size oriented headline scaling is a fallacy, because energy relates to mass (be it striking force or metabolism), not length, and mass scales with volume, and volume scales to the third power of length for three-dimensional-ish shapes (which are most animals).

So, say, the human arm is perhaps 100 times larger, so the headline-scaled striking speed would be 9000 m/s. But it is also approximately a million times heavier. The ant would hit with 0.02 J, the human arm with over 200 MJ, a punch so strong you could literally stop (and presumably completely destroy) an airliner in landing approach with one blow.
There is another great video that goes into detail on his Louisiana is trapped in a tax incentive hell because of how they award these credits:

https://youtu.be/RWTic9btP38
This article seems to be putting on some strong rose-colored glasses. It appeals to the idea that people in the past all lived in beautiful, long-lasting buildings. The reality is that the long-lasting buildings are the only ones that still exist. The bulk of humanity has always lived in cheap construction. Affordable housing is not a bad thing, especially with modern fire codes.

The last paragraph starts with "For centuries the quality of their buildings and a certain permanence set cities apart". That's a really good joke. The author even points to this earlier with "The sameness [of 1+5s] isn't like East Berlin's "Plattenbauten" (precast concrete buildings) around Alexanderplatz, nor has it the uniformity of some of Baltimore's rowhouse neighborhoods." I'm legitimately not sure whether those cheaply constructed neighborhoods are supposed to be positive examples or not.
The author never used the phrase "glass bead game" -which pretty well describes quantum computing's relation to anything you could consider science or engineering. I guess he does use the words "Alcubierre warp drive" which is about right, except we don't have 1000s of Alcubierre warp drive experts running around publishing papers and pretending like they're not playing make believe.
Static is pretty good.
Google to vet political advertisers for European Parliament elections
All of the spectacular construction fires in Oakland in the past few years have been this type of construction. The enormous open wood frame structures were like carefully constructed bonfires built of dry wood. Lots of surface area and ventilation to feed the fire once it got started.
> I have no reason to suspect that Apple broke hardware they themselves sold

In fact my own 15" MBP late 2013 has a GFX750, which is no longer supported according to Apple Support [1].

The worst for me is that this didn't withold Apple from pushing the update, so running Mojave with an external monitor is hardly possible now.

> Nvidia is not a "good" company.

Agreed. Neither is Apple.

[1] - https://support.apple.com/en-us/HT208898
Oh GitHub mobile can be pretty annoying. Glad you found it!
The town has a government comprised of the people from that town. If there isn't anyone in the town smart enough to run for government who, as the other responder pointed out simply needs to look for other towns that did something similar and ask them how they did it and who they contracted with, then obviously the town is full of utter morons, and by definition, the democracy in that town is working as designed: the people are getting what they deserve.
we do make money on some of the links but I hope it's much more then that.
People can ask for help finding something, collect and talk about things they are interested in and discover things they may not have found. They can follow people of similar interest or make private pages that they share only with certain people.
Also, we only have affiliate deals with a handful of stores but people can post suggestions from anywhere on the web. We have no advertising or sponsored content and don't track people so that is what we decided on for a revenue model.
There are plenty of pages and wishlists where all of the products are not for one of the stores we have affiliates agreements with, the goal is to establish a community of helpful people but we still need a revenue model.
Ask HN: Is GoDaddy Working?
their help site seems down: https://www.godaddy.com/help

also a WP site on it is down too.
Are you implying that all politicians/politics are part of a play scripted and decided in advanced?
Robinhood introduces checking accounts with 3% interest
These plots seem to be very deceiving. Obviously if you aren't one of the big players like Walmart or Amazon, it may not look as dramatic as it really was. I'm assuming cloudflare is not a cache for those two?
Interactively Pipe Commands Together with the Ultimate Plumber
> If you are a software developer, you have no excuse not buying a Linux compatible machine and using it as your daily driver.

False. I've tried it and it doesn't compare to OS X. Also this SOOOO rich in a thread about Nvidia (which SUCKS on linux). You think you are in driver hell on Mac? Oh boy, strap yourself in.

> Im nearly completely free of Apples ecosystem, thank god.

Enjoy your "freedom", I'll enjoy getting real work done without futzing with something that "Pretty much works (tm)" but has some kind of gotcha. I'm sure the developers here at my work who use a Linux desktop would tell you "It's great, I love it" but somehow I'm the lone developer who doesn't have display manager crashes, complete rebuilds needed, and graphics driver hell. Yeah, I think I'll stick to my "imprisonment".
Doesn't the CO2 eventually return to the concrete when it cures and hardens making it sorta the reverse of crops in long term neutrality? (Generates CO2 on creation but retrieves it eventually as opposes to capturing but returning eventually.)
Rather than stalling while waiting for long running operations (like accessing main memory), it executes unrelated operations while waiting for them to complete. Performance gains are dependent on the details of the design, but are pretty significant in general.
I've had an idea floating around to generate a stable coin for a while now and would love to get some feedback: The idea is simply that everyone can mine new "tokens" (for lack of a better word) by running a proof-of-work algorithm and broadcasting the solution to the network (just like the block mining in Bitcoin). In every new block all verified token generations are payed out to the respective addresses. In the long term the value of these tokens would be limited on the upside to the cost of the PoW algorithm. The difficulty of this PoW algorithm would remain constant - unlike the BTC PoW algorithm which adjusts with the hash rate.

Two issues: 1) This scheme would only work with a PoS algorithm for block creation, because in a PoW system the security depends on the block reward (which would be low in this system). 2) There's not really a lower bound for the price of this token - the intrinsic value depends on it's usability for payments.
Suppose you do a+b. If a or b is not available the cpu will run the instruction after the a+b instruction. Otherwise the cpu is waiting on a and b to be available and doing nothing.
Seems to not be mutually exclusive...
I don't think I've ever seen a nicer place charge me actual money for wifi, but usually they force you to sign up for their dumb membership club or newsletter (so, not exactly free either).

My last trip I had a box of those soylent shakes sent ahead of me and just used those for breakfast - reasonably healthy and tasty enough. Better then the free breakfast for my use case anyways.

I'll second Hilton on good customer service though, definitely one of my preferred chains. That and the business oriented Holiday Inn Express or whatever they're calling it now.
> The Centralia mine fire also extended beneath the town of Byrnesville, a few miles to the south.

What an ironic chain of events to happen to a place called Byrnesville.
Oh, perhaps I misunderstood your question.

If you mean why can't I completely replace them with newly built containers, it's because they are complete but rather old OS images with years of configuration history in them, running specific versions of mission critical applications.

They are older than LXC, and were originally run on real servers, then under chroot and UML, then under KVM, before LXC or Docker were a thing.

To be tinkered with most carefully. As much as I would like to restart from scratch, with new versions of everything, experience has taught me it would be unwise to do it in a hurry, or without extensive testing.

So yes they can be replaced and will be eventually, but it's not a small job and will need time scheduled to it.

For the time being it's the Right Thing To Do(tm) to keep the existing images still running as they are.
Things always change. This is unavoidable.

You can either work to minimize the amount of change you'll have and identify the places where it's more likely, so you can add flexibility there, or you can be caught by surprise every time and pray that the next change won't suddenly throw years of work away. Both are perfectly sane attitudes on different contexts.
Most (all?) modern processors utilize out-of-order execution. The main advantage is that it increases IPC (instructions per cycle) in the long run.

The high-level idea is that you queue up your instructions in a table of sorts and execute them as they're ready (i.e., based on dependencies). You then re-order the instructions at the end of the pipeline.

The main challenges with this technique are: (1) handling exceptions and (2) speculative execution. For (1), you can use a re-order buffer. For (2), you would typically flush the instruction table noted above.
>society will get sharply stratified into the 'watched' and the 'watchers' and the latter will get access to nearly limitless data and power...

Don't kid yourself, even the 'watchers' will be 'watched'. The people bringing all these systems together will not be your local yocal Barney Fifes. They will be professional and highly intelligent technical teams whose members have likely studied little other than security and intelligence gathering for their entire professional lives. These are not the type of teams that carelessly leave obvious security holes like that laying around.

Taken as a whole, the technologies coming out today will enable surveillance regimes the likes of which even the UK and China never previously would have dared to dream up.
The Flaw Detector
What to do if you find Coinhive on your website?
Yeah, because the CEOs, Politicians, etc... are definitely the people walking around in public spaces or delivering packages or buying stuff from stores.
It's been debunked.
Pickup trucks are almost unheard of outside the US, except in the countryside. SUVs are much rarer as well. Somehow people get by.
I would argue that it was a fiat system modeled somewhat closely to the U.S. monetary system.

Point is that DAI has economic incentives in code to keep its price in check.
I would consider asking on /r/golang or the golang-nuts mailing list.
As a native austinite and engineer I completely disagree. The eastSide was a terrible place before. Going into pan am park was a no go at any time of the day. Comunities and infrastructure were dying in eat Austin. Also, It had extremely low home ownership rates so the lower class didn’t even own homes in these areas but made money for westside landlords.

South congress was full of crackheads and prostitutes as early as the 90’s. We had real urban decay. Now we are growing like crazy and if you’re willing to work hard any immigrant can get a construction job and make a great living for themselves.
Mars' Olympus Mons is so massive that you can't see the summit from the base