skysight-inc/HackerNews huggingface dataset:
Speaking as a young engineer, I can tell you many are already looking past microservices towards things like AWS Lambda, AMQs, and BaaS, which make a great deal more sense. Why? Because it helps reduce dev effort down to purely the logic you'd have to write no matter what, with better guarantees about reliability and scalability, and less maintenance. I hesitate to say 'serverless' because that still feels somewhat out of reach, but that's the direction things are trending towards.

I also get the sense that a lot of purists moulded in the ways of yore are alarmed at the waning relevance of their skillset. This to me seems like a bigger problem than the evolution of software paradigms.
I've heard that mobile phones are filthier than toilet seats, and plenty of young children have them these days. I've seen babies too young to walk or talk given electronic tablets to distract themselves with. I wonder if the trend toward youngsters interacting with electronic devices that are rarely if ever kept sanitary will help keep allergies at bay?
Really? The Fillmore always struck me as a really nice place.
I think it's similar to companies needing a different kind of CEO to bootstrap a company than is needed to scale up and streamline one. It's also very difficult to know which area and how much to risk on something new when you already have a successful product.
JQuery Mobile versus NativeScript
Reminds me of the old accounting joke.
CFO -> CEO We have a major problem, recent price cuts mean that we are now making a loss per unit on our major product lines.
CEO -> CFO Don't worry about that, We'll make it up on the volume!
There is a freenet site that lists torrents, magnet links and inserts the file into Freenet but they use the kat API so I assume it's dead too. It shows that a Freenet based site could be workable though.
QSAR sounds very interesting, if I encounter a failure in later stages of drug development - can I feed that information back to the model? See I'm trying to understand if the concept of a unit test is present in the drug development field. Unit tests watch your back - whenever a bug is found you are required to both fix the bug and write a unit test which ensures the bug won't happen again. If QSAR has that - my article may well be redundant.
The author, me, knows a bit about drug development. But I do know about software development. If you find this not useful, read on to the next article.
> "Why is this linked-to from HN?"
This is linked from HN because I've published it there. I guess you can contact the administrator to notify him/her that someone is wrong on the internet.
New link:
https://medium.com/@osharav/develop-drugs-like-we-do-softwar...
This part is business, not programming.

My biggest salary negotiation was part phone, part email. But the relationship was collaborative, so it worked.
That isn't what's at stake here, however, so the hyperbole is unneeded.
Having been part of projects that grew large over time and are composed of too many components, I understand why this is done. It reaches a point where you can't go to each open issue and see whether it's still relevant in the context of all the new and different technical changes that would have gone in during that period.

That mail does seem to point to a place where users can report this afresh if it's still relevant. So, not a bad approach, to get these bug reports to hopefully in a more relevant and manageable state.
Some manager received a bonus for closing so many bug reports. Wonder if he took the team out for pizza and beers.
My sister lived in Daybreak, and one time I came to visit and ended up a half block shifted from her place. The house looked identical and I almost let myself into some random strangers house. I decided to knock at the last second and was quite surprised when a stranger answered.

It felt a little creepy, things were just a little too uniform.
We're at least two or three generations away from any of this. Hell, slavery's been abolished for five generations. Five generations ago, my family was poor-as-a-churchmouse country bumpkins (still are, by and large). They didn't have any education, and they got drafted to fight in a war they didn't give a tinker's damn about to fight and die on Little Round Top and a dozen other places in Virginia, Maryland and Pennsylvania, and many of them died.
If you read my top-level comment you'll see that I agree with you 90%, but careful not to throw the baby out with the bathwater.

There are legitimate reasons why having those fiefdoms is beneficial despite the overhead. Especially in a SaaS world where you are not distributing binaries. Being able to use different languages for different purposes, and to deploy them to different hardware can be quite a bit more efficient in terms of hardware costs at scale. Also there is something to be said for "you write it, you run it" as it makes developers more careful and decreases finger-pointing. Again, don't take this as a rebuttal, the overhead is potentially a lot, but if clean interfaces can be determined and makes sense from a high-level business perspective then there can be a net gain.
You say it as if it's a bad thing... Compared to the alternative, fiefdoms really are a wonderful thing!

I once work for a giant fortune 500 corporation. Our department had a good 300 developers, and had been writing code for years. They had built the whose system using the classic, box-box-cylinder architecture. There were hundreds of little top tier 'services', but in practice, they all shared the same database, had to be deployed pretty much at the same time, and version upgrades had to go in lockstep. Every so often, database changes were necessary, and the world would grind to a halt for months to make the system still work after the migration: It was awful.

On top of this, having everyone using one stack really meant that a council of elders got to make tech decisions, and everyone else just did what they were told. This built a giant hierarchy. People near the top would never leave, because nowhere else would give them that much power. Talented developers would take years to gain influence, so they often just left. What remained was developers with no ambitions other than getting a paycheck... it was horrible.

The alternative was to let people maintain their own stacks, as long as they provided interfaces that other people could call. By limiting how much code could talk to a database, you didn't need negotiations to change something: Teams made any change they wanted as long as they remained backwards compatible, and then had to lobby users to upgrade to newest API versions if they wanted to remove the backwards compatibility mess. It was awesome in comparison.

A gigantic place won't have those problems, because they can invest money on making whatever tech decisions they made tenable: PHP is slow? Let's build a new runtime and compiler, says Facebook! If you are tiny, you don't need any of this BS, because if your team of 8 engineers can't agree, your company will fail regardless. But when you have 200 engineers, it's giving people more control over a piece of the pie or bleeding talent.

The one thing you still need to do is make sure teams have the right size, and people have enough accountability, that the product still works. You also need silly amounts of data marshaling and error checking compared to the monolith. But the terror of a company that can't hire engineers because the only way to have any control over your daily life is to have been there for 5 years is just hard to compare. When people say they don't want to work big corporate gigs, what they really mean is that monoliths become soul sucking.

So yes, I give thumbs up to fiefdoms, just like I'd rather have inefficiency in a republic vs a theoretically efficient dictatorship.
01001110011000000101
I would imagine dividing the column in to ten segments would leave them rather small and difficult to hit accurately, on screen keyboards for instance require a certain amount of prediction to guide missed clicks; a fader lets you dial it in. If you've ever played a stringed instrument (fretless that is), you will know that it's easier to miss your note by a little and then roll your finger to adjust than it is to simply get the note first try without some kind of tactile feedback like a fret, or in the app's case, a physical button.
Adoption. By offering a standalone solution that can be adopted at the grassroots level they hope to drive adoption faster than any other way.

This is why they're including batteries instead of telling customers to feed excess energy back into the grid. Feeding into the grid is technically more efficient and doesn't require all those batteries, but does require the headache of interfacing with your local utility.
> Have staggered work start and end times and "peak usage" will be a less pronounced peak.

This would have benefits today, but still rarely happens. A very small fraction of massive businesses have shift workers do this to more efficiently handle the volume that transitions between shifts would otherwise cause, but the vast majority of businesses do not. I don't think self-driving cars would change this.

> Also add in more home offices.

This would help today as well, but I don't think self-driving cars will change this either. (And if they do, it might not be in the direction you'd hope: self-driving cars might cause people to tolerate longer commutes.)
Geohot is pretty much claiming to do that!

http://www.theverge.com/2016/6/6/11866868/comma-ai-george-ho...
What funding from new shareholders?
010000000111000101011
The Fillmore has a long history of changing ethnic hands. Once upon a time it was a Japanese neighborhood. Once upon a time it was a Jewish neighborhood.

When people discuss the Fillmore and its history, that discussion tends to start at roughly 1945-1950 when there's just suddenly a black neighborhood. Like maybe it materialized out of the aether as a jazz center or something.
Few years ago I bought Windows 8.1 from some online store. Used the activation key, worked fine, after few months needed to format the system and reinstall windows. Activation key won't work anymore, called the MS support, told them the key, found out that the key was from some "student/education program" and is no longer valid... WTF.

For last 2 years I have been using macOS (osx) and no crap of activation there and most importantly once you understand the abstractions of UNIX you wouldn't want to use any other architecture :)

I guess some major problem with Windows is the business model of OEM around the OS.
Go south of Turk along Fillmore sometime. At night. You'll see the McD's and the police station mentioned.
You're not alone. I appreciate Anaconda, though I happen to use WinPython right now. In fact I keep a WinPython installer in my pocket on a flash drive.

The most important thing is that I can get a relatively vanilla Python program running on any computer that I bump into, without creating a potential future headache for the person who owns that computer. WinPython is almost like an isolated environment.

But at the very least, if their instructions ensure that you can get an installation to the point of running the tutorial programs successfully, and learning Python rather than fussing with installers, I'm OK with it.
Majority of that use is on tablets and phones with native apps now and not on browser based flash games.
You might want to seek some help. Unless you're just being dramatic here for effect, there are some red flags in your post such as not being able to get out of bed, being filled with self-loathing and despair, etc.
> Should we come up with a name for the "oversteering" used to recover from a turn

Ignoring the reductio ad absurdum, then if you're referring to how you have to steer the handlebars further into a turn in order to straighten out, there is a name for that: counter-steering. :)
I mean finding the equivalent of unit tests in drug development. If it's already there - great. If not - let's file a Jira to research that backlog item
Vim-Pokémon – Pokemon might be in your open file
I was about to post that these exploits should be substantially mitigated by iOS sandboxing (you can get arbitrary code execution, but can't get out of the exploited process's sandbox without a second exploit), but then saw CVE-2016-4627 [1] also in the 9.3.3 release notes, which is a local privilege escalation exploit that allows arbitrary code execution with kernel privileges.

There's not a ton of detail out there on the second exploit, so I'm not sure whether or not they can actually be paired to gain kernel privileges remotely. Still, more than enough reason to take these issues seriously and make sure you upgrade in a timely manner.

[1] http://www.securityfocus.com/bid/91831
Which is exactly what you cannot do, the moral and legal constraints dictate that we probably need some other mechanism.
Does anyone know, whether Skype is still running on Postgresql?
If so, would be amusing.
My Grandmother's Grandmother was a slave and my Grandparents fled the segregated South where lynchings were common.

Ever see any of that horrifying Civil Rights Movement footage? A lot of those people are still alive. The victims and the perpetrators. All those people protesting the integration of schools, throwing things at harmless black children? Still alive.
Well, to be fair, the AI probably tried somewhere over several millions of times before coming to whatever conclusion it reached in its training process
Blind "cause of death" stats are fairly meaningless.

I believe a better standard is to look at QALY -- quality-adjusted life years. That deducts relatively little for, say, a heart-attack at age 85 (you're already at your maximum life expectancy), but would put a heavy weight to, say, a pre-teen girl crippled by an auto accident, but surviving for life.

https://plus.google.com/+MarlaCaldwell/posts/BUZH36tmjso

http://www.cbs46.com/story/31596864/two-children-hospitalize...
Abuses? How about "utilizes"? The subsidy is there to get more electric vehicles on the road.
I like living in the suburbs. Dense urban areas create anxiety for me.
Yep. I lived a couple months in Tenderloin (little Saigon, to be specific) and the stories I could tell you. It wasn't uncommon to see people lighting up crack pipes in broad daylight, but I never did see anyone shooting H out in the open.

There was a closed building across the street, and most days a fence would sell stuff on a blanket in front it, with stuff they stole out of cars - or at least I assumed that's where he got them, because it was always CDs, travel mugs, umbrellas, jackets, etc. They're even on Google street view:
https://www.google.com/maps/@37.7835518,-122.4176013,3a,15.7...

I never had a problem with crime, probably because I'm a big guy and I never walked around after dark, but I knew people who were mugged nearby. I was paying $1350/mo for a (nice) room with a private bathroom.
Now, yes. I live in Western Addition. Before I lived in the nice part of Soma by the Ballpark. There we still had the mentally ill and feces to some degree, but not the rest.
>> The bigger issue is that they let it get this bad. In order to get this this point, they would have had to systematically fail triage bugs when they come it, fail to track them as they're fixed, and fail to rectify the problem for over two years.

In reality, it's not that easy. There have been times where, in projects that I have been involved, I wanted to fix a certain issue but the time required to setup, reproduce, investigate, fix and test against that and other versions, just adds up to a point where you cannot focus on the other equally important (new development) tasks at hand. So overtime, issues which might look easy to fix or interesting, do get piled up.
I think they're removing seats out of desperation. I've was hearing the planned capacity was many, many times smaller than the current ridership. It can take lots of money, political sway, and quite a few years to catch up.
A quick thing that can be easily dispelled: minority groups didn't voluntarily move anywhere from '34 to '68 [1], because the FHA policy of redlining prevented them from getting a mortgage in predominately white neighborhoods. Shockingly or not, the higher quality property was reserved for whites.

'68 was the end of formal, legal requirements to disapprove of mortgages in heterogeneous communities (for lack of a better term). There's plenty of evidence that the practice continues even to this day, informally. [2]

[1] http://www.theatlantic.com/business/archive/2014/05/the-raci...

[2] http://portal.hud.gov/hudportal/HUD?src=/program_offices/fai...
I was hoping you'd prove that most people consider Skype to be secure, for A, because that's what you claimed. As for B, there are many other options, I don't really know what you mean by "they would be able to trust it without need to fully trust the other parts envolved (contact and service)." Are you saying PGP is backdoored? Do you know something we don't?
The computer doing this is the result of smart people working on the problem.
I'm pretty sure New Vistas is really just a new place to play Pokemon Go.
Experience with car share services suggests this isn't the case.

Source: Personal conversation with ZipCar analyst.
>Electric cars cause pollution; they run on mostly coal or natural gas.

There's also a ton of energy going into the cracking of crude into its constitutions parts before it even enters the supply chain for use in ICE vehicle.

Further, centralized power generation does a much better job at filtering and removing toxic elements from its discharge stream than gasoline/diesel vehicles filtering mechanisms do.

Notwithstanding the above, fossil fuel electric plants can be removed from the grid and replaced by cleaner energy solutions without having to replace or modify the consuming vehicle.
I have stock in Solar City and I don't care if I lose it all. It's not my life savings though. I invested because I enjoy day dreaming a similar dream to what Musk must be dreaming. Like any great science we just have to try and be excited, together. We can all banter about economics, rationality and history but I'm stoked. Who cares. I don't see how Tesla or SolarCity failing would lead to mass starvation or anything so let's strap in and be pumped!
Didn't they say that certain browsers render elements differently and they wanted a consistent experience?
Please think about what you are saying when you write "You can use it irrespective of how an ill-advised majority of developers think Javascript/Node/Angular is good."

Most of the places I work will only allow the use of a language that is in the top 10. I am not allowed to introduce Clojure, because it is not popular enough. But if I told management "We should use Angular" that would be an easy sell. You sentence would be more accurate if you had simply written:

"You can use Javascript/Node/Angular irrespective of how good they are, but you can't use something that is great because a sometimes ill-advised majority of managers base their decisions on their estimate of future risks."
Exactly! It's amazing how unaware Mac zealots are of other operating systems. They may learn something if they'd shut up and listen.
Excuse me? I grew up in Detroit and Flint, and come from a broken family. I earned my way up and out of those particular hell-holes, making my way to the East Coast and lately the West. Please, do tell me more about how I haven't investigated the issues of Black families and communities being targeted for acquisition, etc.
And they will go the way of Nokia and Blackberry if those practices don't change pronto.
This seems like it would preclude people who love what you are doing, but also love to do things after work that aren't around programming.
So you're saying the true Zion / New Jerusalem of the end times will come about organically rather than in a pre-planned fashion? Fair enough.

(I'm not up on my eschatology enough to get into this further.)
The specifics probably weren't in his plan, but in various interviews he's talked about the consumption of energy (vehicles) and the generation of energy (solar) as being two sides of the same coin. Elon is the one that told his cousins to start a solar company after all.

IIRC he originally saw three major fields to move forward on: the Internet, Transportation/Energy, and Space. By the sounds of it he was thinking of these as early as high school, to at the latest some time after he sold his first company (Zip2). He did the Internet thing pretty well, now he's working on the other two. This is someone who does think on these scales. Keep in mind, as the article itself points out, that you're an idiot if you think starting a car company is a good idea. Energy was the whole point all along. A company for its own sake isn't in Elon's DNA. That would probably just be too boring for him.

Whether this specific merger is a good idea or not is a different question. And I also don't think the emergence of cheap supercomputers in the form of geek-subsidized graphics cards and their applicability to a particularly effective machine learning genre would have been predicted by anyone.
> time required to setup, reproduce, investigate, fix and test against that and other versions

And that's not the case again. I already provided all information to reproduce that bug easily.

PS "bugs", actually. They've closed several bugs that I reported, though notified me about one only.
Semis sound like a better market for hot-swapping and renting your battery compared to consumers. The rollout is a bit more straightforward since the travel routes are more obvious (weigh stations or truck stops).
Oh yeah, I don't think it's bad research going into this. I mean I've been writing software professionally for almost 20 years now and I am super excited about (for example) containerization and other trendy areas. I think it's great that people are pushing the boundaries of SOAs, and I think microservice is a good term describing how the boundaries are being pushed. We will all benefit from the improved tooling and experience gained.

My only complaint is this ostrich mentality of declaring ubiquity and ignoring the downsides and unsuitable cases. I suppose drinking the koolaid might be necessary to really buy in and push the paradigm forward, but sometimes it feels like willful ignorance.
hstore has some stuff that's missing from JSON.

My favorite hstore feature is that you can produce a diff simply by using the minus operator. For auditing a table, in an ON UPDATE trigger you can simply do

previous_values = hstore(OLD) - hstore(NEW)

previous_values will only contain columns that have changed, with their old values.

You can then restore the row to its previous state by doing PREVIOUS_ROW = CURRENT_ROW #= previous_values.
I'll second this. Having suffered from chronic depression for decades, those symptoms are very familiar.

While there are always ups and downs in life, general disconnection with the world would be good to dig deeper into.