skysight-inc/HackerNews huggingface dataset:
It is not that simple. Often increased demand can lower prices. Economies of scale and all that. For example if you cut total airline passengers to 10% of current numbers, over time prices would stabilize at a much higher level for an individual ticket.

I would imagine that the 'bottom' of the market would grow significantly. As businesses targetted UBI recipients. UBI communities established in cheaplandville, midwesternstate.

Not to say that there wouldn't be unproductive market distortions. Primarily people leaving the workforce to live on basic. Who chooses to work pest control when the alternative is basic?

It would also further stratify the rich/poor divide.
But I love the way they're dealing with it. :D it simply feels human from such a big company. Kudos Google
There are so many articles like this, and all of them focus so much on prescriptive rules for commit messages. There's a similar set of articles on how to deal with branching and merging. Somehow, everybody comes to slightly different conclusions.

The discussion that needs to happen before this is to understand what tools you want to make available to your developers in the future. Using git's history as a first class debugging tool is powerful, but it's by no means mandatory to provide. There's also a real cost to providing each of the tools.

- Do you want bisect to be available? Well, then you should have most commits represent a fully-functional version of the software. Consider squashing branches when you merge them.

- Do you want narrative documentation around strange choices? Fine-grained commits are a great place to put those thoughts, but they may discourage devs from writing those thoughts in inline comments.

- Do you want ownership via git blame? Line-by-line changes may help you identify who wrote the code, but that might prevent your developers from ever fully transferring ownership, which could create bottlenecks in startups that have a few long-tenure devs and a lot of recently hired devs.

I really like to think of git history as a context tool, like monitoring or unit testing or documentation. It's worthwhile to sit down with your team, define what you want them to be able to do with commit history, and build your commit style from there.
My mom has a British/Indian accent but I've never even been there: there are a lot of less common words that I didn't even realize I said differently until I was too old to feel like intentionally changing it: rather with an 'ah', calcium with a 'sh', occasionally unconsciously spelling things "theatre" or "centre" or "harbour" (I guess a good chunk of the books I read growing up were from British publishers? I don't really know). I don't know why but I always managed to be surprised by how shocked people's reaction is to these pronunciations and spellings, especially because I've spent my whole life in California surrounded by immigrants (I'd say the percentage of friends I've had with parents born in America is in the very low double digits).
The assistant that promises solving any problem within 7 days
I grew up in the Bay Area. I've had to look for parking in the City a few times, but eventually learned to avoid it like the plague. I worked in San Francisco for almost six years and never drove to work even once.

Public transit is the only sane answer. That's why I mentioned trains. When I'm in the Bay Area, if I'm going to San Francisco, I simply refuse to drive there at all.

Hotels have gotten insanely expensive in the City proper as well; when I go to events in San Francisco, if I'm paying for lodging, I'll often get an AirBNB in Oakland near Bart and take that in. Instead of $300/night, I get a nicer place for less than $100/night, and the BART ride is only about 20 minutes.
> i'm new here and have no idea how long comments are allowed to be. there's a lot to say, but i'll try to be succinct. (and probably fail.)

FWIW you're fine, this wasn't a particularly long comment at all.
I've been writing commit messages this way for a little under a year (I think this is the same guide I used when I was looking for a more consistent form to write them and to avoid the dreaded -m "Fixed some things").

One thing I noticed is that it's increased my confidence in my commits; at the moment that I go to write the commit message because I'm describing why I made the decisions I did it breaks logical inconsistencies between what I've actually done and what I think I've done. If I'm able to explain all the change I'm much more confident that it's correct.

Another is that bad commit messages have trained people not to read them. Often people will ask why I've made a change and then discover that the commit message contains the answer to their question!
Great idea, I'm gonna steal this.
Spring Cloud Stream improves routing to handler classes, metrics, avro support
Yeah, you're right. But frankly, I don't care what people think about me. If what I am saying is true, they can think I am crazy, but (hopefully) the words will stick in the minds of some, and in time those words will be proven right.

Of course, there is also a risk that sometimes I am wrong. There are things that I believed to be true that were not, and I've gone back and told people so. Pursuing truth and being transparent about my mistakes and missteps builds trust.

People may not like me, and I'm fine with that. I would rather have their respect than their admiration. If they do not respect me, then I will do them the courtesy of keeping my opinions to myself. I don't waste my breath on cynics.
Speaking of watches, the Breitling Emergency has a built in locator beacon. Not exactly cheap though.
Massacusetts sucks
Anthony Bourdain didn't have a savings account until he was 44 years old
It means compare. So typically you'd use it to give a contrasting example. In this case it seems to be (mis)used to mean 'see' though.
> Breaking into tech companies is only about rehearsing Cracking the code interviews, and once you're in, you have no guarantee to make any sort of career. You'll probably be out soon because things move too fast and the turnover is insane. Your next job is gonna be difficult to find because the next tech company won't care about experience

As someone who's worked as a software engineer in the bay area in tech companies this is 100% not my experience at all. Though tech interview definitely matters, experience also matters and the turnover is not insane. All of my coworkers who I have made friends with are still in this business and I've worked at a few different places. I just don't think you have any idea of what you're talking about.

> you have no guarantee to make any sort of career.

I have quite a good career. Others do too.
"User scrolls with two fingers on a touch pad" This was so weird for me at the beginning haha Always mixing up and down :D Anybody else had this problem?
Epic, Cerner and Meditech are the largest EHRs and they combined control just about 50% of the market. Epic and Cerner tend more towards the Academic hospitals and Meditech and McKesson (#4) tend towards the Commercial hospitals.

There has also been a ton of incentive payments from CMS that have almost exceeded the EHR industry as a whole.

There have also been quite a few big switches from the 90s to today, a bunch of them from Meditech/Epic/Cerner to others, so it can definitely happen.
Indeed. There is more at the Google Drive forum. Seems to be limited to the Windows client from the reports. It could be serious as there are reports of folders disappearing.

https://productforums.google.com/forum/#!forum/drive
European team announces superconductivity breakthrough
He doesn't take 150 pills a day. He just writes that he does, which is worse.

Source: eaten with him, carried his luggage.
> 10000, 200, 20

You don't notice the pattern? The first big bump was 10,000 years go. The next one was 200 years ago. The third one was 20 years ago. It does seem like it takes less an less time for the world to work out what's unnecessary about social organizations. If I naively extrapolate, within decades we'll have period where we have profound cultural shifts every year or so, then every week.

Frankly, I think we're already in the once-a-year period it's just that profound social shifts aren't quite as newsworthy as they were in the nineties. And the adoption curves are still on the order of decades, so while there's a new game changing structures every year, it still takes 20 years for it to disseminate. But the successor to a structure is getting created almost faster than the original is getting disseminated.

This is why people talk about the singularity. If these trends continue, it means we're headed towards a moment of "max everything". Opinions differ on what max everything will look like. I don't think "AI superintelligence" will be a thing, others do. But it doesn't seem crazy to expect things will look very alien.

We're headed towards one, globally connected, mind. Some will opt in, and life will look very different for them. Some will opt out and things will more or less freeze in a vaguely 20th century form. So I guess in that sense "everything will be different" and "nothing will change" are both right, depending on what kinds of person you are.
Also get the Android APK and decompile it.
Is it really that big that we need to talk about "scaling" it? 4-5 hours of processing time is a lot... I mean how many transactions would they do on a normal day?
Stories with lots of comments are rank-penalized. "Whiteboard coding is bad" submissions attract a lot of "me too" comments and quickly fall off the first page.
I'm currently working on my thesis, I'm trying to design a radically different take on EMR/EHR systems - http://barnett.surge.sh/

I've come to realize healthcare software is a significantly trickier problem than most realize. Not in terms of technical possiblity, but other factors.

Building healthcare software is really hard - which seems like such a paradox, because surely ensuring highly trained individuals have half decent tools would be a huge goal for society - but almost all healthcare software is still frankly, terrible.

After heaps of reading I've narrowed it down to 3 reasons why healthcare software is so hard to build.

1 - Modern healthcare is complex, and varied. Building any healthcare softawre is no easy task, even simple systems have many other systems to integrate with. But what makes this worse, is that no two places do healthcare quite the same. Between regions, and institutions, healthcare can vary a shit ton.

2 - Healthcare is risky. Sounds obvious, but if your software fails, people die - but this risk creates an attitude of "dont touch it". Changing systems has such a risk, that institutions will use the same software until it's so out of date its not funny. This impeeds improvement and innovation.

3 - Healthcare software is hard to sell. Not in the sense that its unprofitable, but that it takes ages to get users. Say if I made video editing software - I could get professionals trying it out tommorrow. However, if I make a PMS, I have to sell it to the entire practice - not just a few keen doctors. From making contact to actually getting a small practice using your software could literally be years - making it super hard to enter the market.

I've been working on this topic fulltime for a year now - and I must admit, I don't have the golden answer. However, I'm designing a system as a response to these factors, an alternative to interoperability, and would love to talk anybody in the industry about it.

http://barnett.surge.sh/

eliot.slevin@gmail.com
If you want to search for the history of pineapples,
you don't need 100 sites with the same info.

"Pineapples grow from a plant in the tropics."

"Pineapples are grown in equatorial countries."

---

"Pineapples, when ripe, have a very sweet taste."

"Ripe pineapples have a high concentration of sugar."

---

"The etymology of the word for pineapple is 'excellent fruit' in the language of Tupi, although the english English translation is an aberration, with a stem of 'pine' due to it's resemblance to a pine cone."

"Most European languages name the fruit using the root word 'nanas', from the original native language where it was grown. Many languages have adapted the root word, although a few have a large degree of uncertainty, such as the origin of the reference to 'apple' in the English word."

---

It would need a fairly decent AI to recognise the commonality of information in these examples.
America First – The White House [pdf]
Unfortunately with the consolidation into medical "groups" that has been going on among doctors and with the hospitals offering "deals" along side those vendors they use for the doctors to adopt them, a lot of doctor's groups have adopted whatever system they are most integrated with's EHR.

There's a ton of slimy dealings going on sadly.
Here's an idea (although probably an unpopular one around here): if a site is responding to your scraping attempts with 403s -- a.k.a. "Forbidden" -- stop what you're doing and go away.
> One way or the other, the effort will bear fruit I think

Or even if it's just to give us agriculture, mass production, electricity, sabremetrics and iPhones.
I worked through the labs at https://pdos.csail.mit.edu/6.824/ for fun. It's more along the lines of "How can we write a distributed fault-tolerant database?" but you might like it anyway.

Lab 4 is a beast with more lives than <insert metaphor>. The moment you think you've finally written your distributed system correctly, the unit tests will prove your service fails during XYZ network partition topologies. It's very worthwhile to be forced to think about issues like that and to design distributed systems for correctness.

But to address your question more directly, it's generally just a matter of scaling your service as much as possible on a single server. The server has finite resources (CPU, Memory, network, disk) so you either know how your system consumes those resources (because e.g. you wrote the service, and you know it uses O(n) memory w.r.t. the workload) or you graph your usage over time and try to predict when you'll exhaust your available resources. At that point you can usually think of some straightforward optimizations, which keeps everything on a single server. But eventually you might run out of resources with no obvious path to optimize it, so what then?

It depends entirely on your service, but typically you can just use off-the-shelf software to scale to multiple servers. For example you could set up three servers, each running Redis, and have Redis keep a list of "work to be done." Then your central process just farms out the workload to each of the three servers round-robin style, for example.

But at that point your service becomes a lot more brittle, e.g. you'll need to set up a failover solution so that your cluster can survive partitions and outages. (Redis uses Sentinel for that.) So it's worth keeping everything on a single server for as long as possible, if you can work out the optimizations to do so, since it's so much simpler with only one server. (HN is still running on a single core and serving 350k daily uniques, I believe, which shows just how effective it can be to keep your architecture as simple as possible.)
Any vim user can profit from visiting https://github.com/tpope?q=vim&tab=repositories and trying any one that looks vaguely interesting.
Feedback on this git commit message convention is welcome, and so are pull requests:

https://github.com/joelparkerhenderson/git_commit_message
It's definitely quite surprising, especially with Google's SRE strength and multiple automated check systems that have been previously documented here.

They often do detailed postmortems so hopefully this one might get that treatment - though given the accidental exposure of the 'not for public release' UI and client they may well not go into much depth with this one.
Wrong, they should be happy it's not 90% or 100% of what he makes. Don't be naieve, why would you deserve anything when there are people who could wipe your life away with the stroke of a pen. Don't pretend you've deserved anything you've worked for. It has been granted to you by those in power as they have seen fit. Your petty idealism has no place in the real world.
> It used to be different, but today their most important offerings have open source equivalents.

Seriously? What about S3, RDS, VPC, IAM? The engineering $$$ (in time) to set up and maintain open source equivalents of these would not be cheap.
Disjoint-Set Data Structure (Union Find Algorithm)
We need some sort of "Adblock for Google search results".
Hospitals in America aren't the main consumers of OpenEMR. Think smaller facilities, and hospitals and facilities outside of the US.
This can't possibly have anything to do with utilitarianism as it is impossible for us to understand domesticated animal utility preference curves beyond "being fed and warm = good". If one is being pedantic, I'm sure one could find many wild species which fare will in confinement, and make a case that it is cruel to contain wild animals in cases where utility from our entertainment does not outweigh their dis-utility from being imprisoned (such as zoos). I'm not convinced that such an argument could be made for domesticated or feral animals.

Utilitarianism is primarily about maximizing utility of a wide spectrum of the population as it pertains to humans and societies and has nothing to do with animals, wild or domestic except for the utility they provide humanity with.

Negative utilitarianism separated from the general concept of utilitarianism is, of course, a nonsense concept in and of itself, since its end goal is non-existence, which makes utility unable to exist.

I'm not familiar with other pseudo-think tanks, so I'll defer to you on that one.
Thanks, justinclift, appreciate it. :)

Hm, I don't see any issues with that, let me see what I can do. Feel free to email me if you have any other suggestions, on the files or documentation (which is being built out now), always could use another POV.
I started using https://commitizen.github.io/cz-cli/ to help me self-enforce this style of commit messages.
I would believe that, but we were hitting the limits of our huge servers. There's only so much QPS you can throw at a single box. These servers were also "pets" as opposed to "cattle", and a big part of the prep for cloud was treating them as cattle.
ThinkPad Compact USB Keyboard with TrackPoint

And a mouse at its side that I am less picky about.
> Excessive standby power consumption is a big problem. There are lots of devices, especially TVs, which consume far too much power when supposedly off

Is this really a problem anymore? I have a five year old 50" plasma, and it draws 0.12 W in standby. That's not "excessive", it's a rounding error. It's 1 kWh per year, or roughly 0.6 kg of CO2; the same as idling your car for an extra 2 seconds every day.
Where Did Vue.js Come From?
I work in this space in the private sector. From my perspective, the greatest impediment in the U.S. relates to our laws regarding PHI. I work on a system with petabytes of medical data -- but researchers can't access it because our laws and regulations don't support it (and thus provide no financial incentive and only risk and lawsuits for the companies holding it.) It's abysmally sad.
I think the one nice thing about the dental world is that "for now" there are still far more independent entities without the ties into hospital groups like doctors and practice groups all have.
If you have a previous version of Rust installed, getting Rust 1.16 is as easy as:

$ rustup update stable

Nah. The old "rustup.sh" script doesn't install "rustup", the application.

Rust isn't in the Ubuntu distribution, either.

Stop rolling your own installer and use the distro programs. You are not a special snowflake.
It seems counterintuitive for a forum to want to penalize threads that actually get traction.
The sequels had some better set pieces. Even though the CGI doesn't quite hold up, the Burly Brawl and the Freeway alone are better than anything in the first. Even the "war scenes" from Revolutions that a lot of people find boring/drag on are better action pieces.

But the big reason I like the sequels more than the first is the "overdoing the philosophical and religious mumbo jumbo" and the "too much boring and confusing dialog". While I will admit the scenes could be better written, I hated how seriously the first movie seemed to take its philosophy and religious mumbo jumbo, and the sequels go out of the way to overdo it and over-explain it seemingly precisely because it isn't actually that serious (it's a set of control systems and metaphors spiraled out of control, just like you would expect from a computer system; it's more like the real world than Tron in this where program names get picked out of a hat from old legends and ancient deities and broken metaphors) and doesn't really mean anything and is almost entirely broken (by design). That's essentially the point of the much maligned Architect scenery chewing, but I think the Cake and Limbo scenes better articulate it.

The sequels even mostly agree that the "battery problem" is a problem and probably a lie. It's a complaint I have with the Animatrix that it takes the battery thing seriously, whereas the sequels seem to hint that even that is a lie the machines spread to control and confuse. (Then again, from the view of the sequels, the Animatrix is likely legends, folklore, and propaganda.)
Try out the https://kraken.io plugin. Kraken.io's optimization is more about fidelity to the original than maximising file size savings.
How We Engineered CMS Airship to Be Simply Secure
Netflix is ditching five-star ratings in favor of a thumbs up
I'm having a hard time understanding this comment. Are you talking about mathematics or philosophy?

I don't understand why finitism would ever be expected to lead to new mathematical insights, since it basically amounts to closing off research directions because they don't have some nebulous quality of "real-ness". I also don't see how finitism has any connection to functional programming.
That would be my bet too. I would say comment/minute, not just absolute number of comments.
A trick I learned from Seriouseats is that you can use a pressure cooker to carmelize onions in about half an hour. The normal stage of onion cooking where the liquid is still coming out of the onion limits the cooking temperature to about the boiling point of water; by using a pressure cooker, the boiling point of water is raised to the point where browning happens even before the water is gone. See: http://www.seriouseats.com/2016/01/the-food-lab-pressure-coo...
The story of every IT project ever...
Unfortunately most of the time you end up having to individualize so much data structure for each deal it's a gigantic pain.
Many instances of us building scrapers are cases where a partner has data or has tools which are only built into the UI or the UI ones are much more capable.

Rather than waiting potentially years for their IT team to make the required changes we can build a scraper in a matter of days.
Should an APK downloader increase an app’s install counter?
Any plans to extend the open source work to electric motorcycles? There's a lot of motorcycle building talent over at https://endless-sphere.com/forums/, but I don't think anyone there is working on anything that's explicitly open source.
I work at a top 10 EMR on the interface engine team. Messages between products require a lot of custom work to align message types and IDs, establishing a compendium of identifiers for external labs and identifiers, but it's not uncommon.
React Conf 2017 videos
>They should change the battery reference to be compute nodes, a la Hyperion cantos.

That was what was originally intended. It was changed to on the assumption that audiences would be too stupid to comprehend it.