skysight-inc/HackerNews huggingface dataset:
If you have bad programmers who are pushing hard on a microservices architecture, you're probably in for more trouble than bad programmers maintaining a monolith. Big, complex monoliths can be tough to work with, but probably overall easier than poorly-designed microservices.
I usually use look ahead negation to make tests that string doesn't match regex.
Similar idea, but I created a text editor that simply blocks you from everything on your computer until you reach a goal: http://writersblock.io
Even still, AIUI the problem with Bitcoin is that a buggy implementation is capable of accidentally hard-forking the blockchain (as demonstrated by https://bitcoinmagazine.com/articles/bitcoin-network-shaken-... ). The existence of a protocol specification document alone wouldn't have prevented that. My question is whether Ethereum actually has some clever mechanism to ameliorate this threat, or whether it's just hoping that the existence of multiple implementations means that no one client ever gains more than 50% market share (and hence any hard-fork that results from an incompatible implementation wouldn't require a central authority to step in to determine which was the "true" chain).
Thanks for being concerned about the quality of HN. Here's what I'm pretty sure was going on:

It's common for boutique publications like this to randomly get posted to HN (often by excellent HN users with long track records). Someone at their office notices the traffic, and they create accounts to start promoting their site here. Obviously that's not a good fit for HN. I sometimes email them letting them know that they should stop because our users will consider it spamming—or alternatively, that they should join the community in earnest and post from a diverse set of sources, including their own.

But that doesn't make the site itself spam. This class of publications often produces articles of general intellectual interest, which is why a user like nkurz would have submitted it in the first place. Such articles are welcome here—they're neither off-topic nor a recent development, and it's good for HN to be well-stocked with outlier stories.

See https://news.ycombinator.com/item?id=11090064 for another explanation re keeping HN weird.
What about doctors using an iPhone to check a patient's files? Would apple have to make a secure HIPAA compliant version for hospital use? What about government use? I bet all those FBI agents are talking to each other with iphones...
Oh I thought this was going to be about the return of segregated dorms this year at the University of Connecticut.
Typed Up CRUD SPA with Haskell and Elm – Part 4: Feature Creep
"60 years ago, we didn't have highways."

Not quite. Here's the US highway system in 1955.[1] Construction of the US Interstate Highway System started in 1956.

[1] http://www.mappery.com/map-of/Pre-Interstate-US-Highway-Syst...
Serious question: what would it look like on a smartphone email client?
20-odd years of Moore's law?
I use regex quite often and I'm happy we have it now more powerful in Chrome. Though, what is so painful in regex is all those flavors of it. I with it was standardized across all languages / implementations.
Not sure what your point is about th shotgun. The point of that export is to keep supporting old API with a deprecation warning while it is being moved into another package. It is temporary.
Ask HN: If there is shortage of developers, how come we don't get clients?
We have started a software startup, did the client analysis, market segmentation etc and started reaching out. We even created a promo - some free development for recommending a client. WHAT ARE WE DOING WRONG? We offer services. We build with Symfony2 (mainly web-apps/backend/backend for mobile apps). Thoughts?
How One Dairy Stock Became a Cash Cow
The "genesis" (perhaps) of the current rise of microservices might be the Yegge Platform rant and the 2 Pizza rule

https://plus.google.com/+RipRowan/posts/eVeouesvaVX

http://www.businessinsider.com/jeff-bezos-two-pizza-rule-for...

Wherein he describes Dread Pirate Bezos' edict:

His Big Mandate went something along these lines:

1) All teams will henceforth expose their data and functionality through service interfaces.

2) Teams must communicate with each other through these interfaces.

3) There will be no other form of interprocess communication allowed: no direct linking, no direct reads of another team's data store, no shared-memory model, no back-doors whatsoever. The only communication allowed is via service interface calls over the network.

4) It doesn't matter what technology they use. HTTP, Corba, Pubsub, custom protocols -- doesn't matter. Bezos doesn't care.

5) All service interfaces, without exception, must be designed from the ground up to be externalizable. That is to say, the team must plan and design to be able to expose the interface to developers in the outside world. No exceptions.

6) Anyone who doesn't do this will be fired.

and

Amazon's Jeff Bezos has a solution for this problem. He calls it the "two pizza rule": Never have a meeting where two pizzas couldn't feed the entire group.

You'll note that nothing in there has to do with technical debt, or unmaintainability of apps, or test suite runtimes, or monoliths, or docker, or any sort of technical problems. Microservices are a technical solution to an organizational scalability / coupling problem.

All too often I see small, co-located teams (<10 people) adopting a microservice architecture because #reasons which are ill-defined.

Docker is awesome, microservices are awesome, but they come with a lot of taxes to pay, and tl;dr - until you know you need to pay those taxes, you should stick with a monolith.
Early startups can do this. The problem for larger (valuable) startups is that the grant of stock would be taxed (as income). Options get around this. (The tax law makes the rather dubious claim that options granted at the market value of the company have zero value.)
Yeah, real estate isn't what it used to be for sure. Especially commercial real estate.
UK consumes far less than a decade ago
If all cars were self-driven and there was a system that allowed them to exchange information, negotiate decisions, etc with all cars in proximity, that would be the ultimate vision safety-wise. I expect that we'll live to see that day. Removing the human factor would be removing the biggest problem.

On the other hand, making this mandatory would also be the wet-dream of most governments. In the name of safety, they could have access to so much information... Just knowing how many passengers the car is carrying, what's the weight of each passenger, and, of course, a history of the coordinates, would open insane possibilities, not all of them good.
But Twitter didn't capture that economic value -- ESPN did.
to be fair, El Niño gave us an incredible year. This winter was extremely dry.
You guys should submit a talk to Spark Summit. Look forward to it.
While I like both Svbtle and Medium, I'd still prefer to
have the blog fully controlled by myself. I'm thinking
about git(github pages)+jekyll because I don't want to
pay for a server.

If you're not paying for a server, you don't "control it" in any meaningful way.
> but I can't think of an application that wouldn't be well suited to React.

A truly complex app where speed is crucial. [0] Like Atom. [1]

[0] https://aerotwist.com/blog/react-plus-performance-equals-wha...

[1] https://github.com/atom/atom/pull/5624
That is redundant- 80% is already covered by the media however
For those looking to learn the basics of Lisp and macro programming from the 'bare essentials', you might be interested in my "The Order of Symbols", a WIP course I'm developing:

http://busfactor1.ca/bin/eturia/lib/sigil/the-order-of-symbo...

Feedback appreciated.
It's "a bit" faster if you pay them. They wouldn't earn a penny doing it for free.
Guess what? Uber isn’t a ridesharing company any more
Brooklyn Judge: Feds Can't Use All Writs Act to Force Apple's Hand [pdf]
Personally, I feel we are approaching the self driving situation backwards. We are so heavily invested in current technology that we are trying to shoehorn existing tech into doin something it was not designed to be autonomous in the first place.

Imagine how much easier it would be, for example, if roads had embedded markers (like magnets or RFID chips) that designated lanes, speed limits, and other road rules and weather conditions. AI vehicles would simply need to read this information and adjust accordingly.

But, unfortunately, this would be almost unfeasible in today's world vecause a) it depends on every car following the same rules and that's impossible if you have human drivers and b) it would require massive investment and national-level cooperation to change the infrastructure.
Not only this. Raspberry pi serves as a good jump in point for embedded development, and there are a good billion more cores to be sold in that area in the next few years.
What Did 2015 Look Like for the Node.js Foundation?
Just as someone using the words "patriarchy" or "cis" tips you off that they're what this guy would call a "SJW", using the term "SJW" in a serious way tips me off that you spend a lot of time contributing to Red Pill subreddits. I can't take you seriously when you start regurgitating reactionary buzzwords from the manosphere (and when most of your citations point to breitbart.com). I think there are valid reasons why one would be opposed to this proposition, but this guy can't seem to make them resorting to hysterics.
If you practice separation of concerns and design your interfaces well, I feel the debate is moot. Who cares if your authentication (micro)service is running locally or on it's own remote cluster as long as it implements the same interface? Clients to the authentication system don't need to know how it works, just the interface. The team responsible for the authentication system can work in parallel and publish
new versions as a library that can be imported by clients.

I unfortunately don't have the need for a distributed system right now. Does anyone with more experience care to elaborate?
That's a fair point, and for sure there are problems that demand a more complex approach.

What I do sometimes see as a problem is that people assume that their app necessarily needs to be more complex than Basecamp, and that arguing for simplicity and "plain old CRUD" approaches to problems is an impossible task.

The best way to manage complexity in a lot of cases is to reject the complexity in the first place. That's not always feasible, but there's a real cost to complexity even when well-managed, and if a "simple application" approach can deliver the same or even 80% of the value, it's often a trade-off worth making.
This was an interesting read in particular to contrast with other startup letters. The focus in the first point on sales and other roles is interesting because I've noticed before these posts focusing on the product (such as http://playbook.samaltman.com/).
The idea that the sales and business will come naturally seems to stem from this kind of advice. It's clear that there needs to be some kind of balance that is usually not talked about.
I'd like to see some analysis of the predicted severity of the accidents for self driving cars.

A minor fender bender at low speed vs. losing control and going over a guard rail at 80 mph are both "accidents" - but have entirely different consequences.

I have a hunch that while human drivers are still better, when they do have accidents some percentage of those tend to be much more fatal.
We've been a target of this attack previously and it's not as simple as email spoofing as email addresses aren't (in Google Apps at least) displayed prominently, firstname.lastname@gmail.com with a corresponding name and profile picture is how we were targeted. Very easy to fall for (especially in companies that aren't strict about personal/professional email separation).
In Toronto I've seen many drivers on the highway splitting lanes because they have no idea where the lanes actually are.
And it's not even $240/year, you need a paid MailChimp plan as well, so the total costs is at least $360/year.

https://news.ycombinator.com/item?id=11170713

"free forever" -> $360/year in a matter of days. Not sure what they were thinking how this reflects on their brand.
Even if it were possible to go buy a fully automated car today, there's no way enough of the fleet would have changed over in as short a time as ten years to make such a ban practical. And it's not possible to buy an automated car today; nor are the research prototypes Google and others have been working with up to a level of sophistication where simply productizing them would yield a fully automated car which could be used as a generic replacement for current automobiles.

I could believe that the first generation of fully automated cars might be available for purchase in ten years.
WebWorker message passing speed tests
This would actually be a brilliant solution. Pledge to release the source code in an installable form (code is useless unless you can run it) if the company becomes insolvent or otherwise stops trading. Ensure data can be migrated. Then, in the meantime, provide the best service possible.
Many early stage startups will use early exercise options with a clawback mechanism.

After the 409a valuation of the startup gets too high, this option becomes much harder for employees, which is why you don't generally see it outside of the earliest stages.
What happens if your car breaks down such that it can't make it off the interstate?

It's the same principle. You try to do the safest thing you can, but yes, at some point a car will fail and be stuck in the middle lane of an interstate because the autopilot fails, just as can happen because of mechanical failure.
Does anybody know if it only invites you if you're in specific countries?
Who is to say that he exploited the tenets in his rentals? Maybe he provided fair market value rents? Just because he's a property owner doesn't make his actions bad.
From the comments section on avc.com:

"Twitter isn't a social network. It's a real-time publishing engine and consumer-customizable distribution network."

I couldn't agree more. For me it's a news reader and occasionally a content marketing channel.
> Imagine how much easier it would be, for example, if roads had embedded markers (like magnets or RFID chips) that designated lanes, speed limits, and other road rules and weather conditions. AI vehicles would simply need to read this information and adjust accordingly.

Speed limits can be defined as metadata on existing mapping data. Existing vehicles, such as Tesla's with their autopilot system and GPS receivers, can "define" existing lanes by refining existing mapping data using their drivers as expert system trainers [1].

You don't need national-level cooperation to change infrastructure; you just need a massively automated system for collecting data and training based on it. Google and Tesla are doing both, just in different ways.

[1] http://www.teslarati.com/tesla-building-maps-autopilot-drive...
If anything, people would think of it as evil hackers breaking into their webcams, the legal solution would be harsher punishments for computer crimes.
How Front Page Hacker News Posts Affect Your GitHub Stars
Thrifty: Thrift for Android, from Microsoft
I noticed that too, almost all are Macbooks and the remaining few Dell. Well it's not the case when all the people used a PDP-7. I've hated that thing called Hackathon anyway, it gives a false sense of victory or achievement. It's no wonder we're having terrifying news from the tech startups.
If you take a close look at both flows you will see that point 1 and point 2 actually explain each other. :-)

If you use React in production and don’t use a bundler, you should. If you don’t use React in production and do use a bundler, perhaps you shouldn’t because it will distract you from learning process. Does that help?

The “need” for flowcharts like this comes from lots of misleading information on the internet about React, not from React itself.

Thank you for your comments!
Same for me, as a Javascript developer. Who knew setTimeout was just setInterval with the internal _repeat flag set to false? Actually, I probably should have known that...
The kids all use Insa and Snapchat, but the vast majority of people use Twitter to disseminate / find information and written content. Snapchat and Instagram are both more intended as "social networks" in its purest definition while Twitter (and FB to a degree) is a social network more geared towards written content and more in-depth conversations relating to this written content.
The conclusion is pretty clear.

Ultimately, the question to be answered in this matter,
and in others like it across the country, is not whether
the government should be able to force Apple to help it
unlock a specific device; it is instead whether the All
Writs Act resolves that issue and many others like it yet
to come. For the reasons set forth above, I conclude that
it does not. The government's motion is denied.

It doesn't answer the question that was on my mind ("Can the FBI force Apple to write and cryptographically sign a less-secure version of their operating system?"), but it's nice to know that the AWA doesn't grant them that capability.
At my last sfw eng job we had two full time writers mostly working on documentation and legacy system diagrams. These people were both contractors, but were employed full-time there before I started and after I left (4+ years.) Like the other poster they may have come from writing firms or just done individual contracting. Maybe contact some head hunters?
Much before the Internet.
To be fair, a lot of those concerns are handled pretty well by traction control systems, etc. I drive in the snow a lot and really appreciate the things my car does to micro-manage traction.

The main rule for driving in snow is to assume everyone else is actively trying to kill you. :)
Is this a joke? This must be some kind of submarine PR to encourage investment in Greece. Greece needs to attract investors and startups by liberalizing their economic positions, not by bs like this.
The urban heat island is my single biggest point of displeasure living in NYC–I so love sleeping the windows open and a cool night breeze in the summer, which would be very possible in my quiet neighborhood of Brooklyn if it were to actually cool off at night.

Instead we have hot days followed by slightly less hot nights, and I run the A/C all night lest I get no sleep at all.
I'd just like to say thank-you for stopping.

I have seen drivers barreling down a motorway at 80mph in pouring rain with visibility of under fifty metres. It made my skin crawl.
I also think a fundamental difference in our reasoning is that I assume a system where each article is edited only by those with an interest in it. Thus all effort and payoffs scale along the same variable. In which articles don't affect each other when it comes to resource expenditure, since the people working on them wouldn't work on anything else.

While it seems that you envision a system that is much closer to classical a encyclopaedia with dedicated editors, where each editor handles arbitrary articles unrelated to the personal investment that he or she has in it. Thus potentially swamping those professional editors with irrelevant articles.

Am I correct?
I'd expect major mechanical problems with robots, like "the vision sensor died in the middle of an interstate," to be about as rare as major mechanical problems with humans, like "they had a heart attack in the middle of an interstate." If not rarer.

We're already okay with the possibility that a human might drop dead in the middle of an interstate and lose control and more humans might be injured or killed as a result. As long as it is not more likely that a self-driving car will drop dead, I don't see why it's any different.

(And this isn't even getting into things like the possibility of catastrophic failure being lower and the options for recovery being much higher. You can run two robots with redundant hardware; you can't run two humans quite as easily. A human who loses vision will lose their concentration; a robot that loses vision can use its last known positions of nearby cars to attempt to pull over immediately in an orderly fashion.)
Strategic Content Marketing Packages
I'm hoping there's a viable SDC on the market when my eldest daughter turns 16 in 5 years
Honestly, given that you can send these kinds of emails out to like 100 people at a time, i'd be more surprised if it didn't work at least once.
If bedroom multiplicity and garage size are key metrics for you... then I guess maybe Solon, Ohio is your kind of place.

People who stick it out in places like SF, NYC or London tend to have different considerations in mind.
1st birthday?
Hold on, if we get this wrong we may be lowering the value of everyone's options and hurting startups. Are there any added protections here against high turnover in infancy-stage startups?

For 30(?) years since the invention of stock options there has also been a de facto added protection against high turnover in infancy-stage startups, where having to rehire and retrain employees is extremely costly. Pre-IPO you basically had to pick a team and take it to that level of maturity before you could leave. You couldn't hop around seed-level startups without giving up your options, usually.

What's changed now is startups are staying private longer, leading to unfair scenarios. E.g. you're at a >$1B company with >100 employees for 6 years and you still lose your options. Traditionally a company would have gone public by that time, but now it's not, so we need a fix.

But if you overcorrect and now eliminate that added protections for younger startups, you risk creating an incentive to leave companies just for the sake of options portfolio diversification. Why bet on one team when you can bet on three, since even 1/3rd of a unicorn that makes it is worth more than 100% of the one that doesn't. And that individual decision leads to higher turnover which can kill infant startups.

Bottom line this fix should be more carefully targeted at what has changed to exacerbate unfair situations, namely startups that have reached "should be public" levels of maturity, yet are still staying private.
I also find it frustrating that this [and similar tools] don't break down by something more granular, such as neighborhood or zip code.

For example, it's not exactly sound to average the price of all neighborhoods in Manhattan.
Sadly these spoofed emails from high ups are becoming all too common.

Shameless plug - if anyone is in need of an open source phishing training solution, I recently launched gophish to great feedback so far, and have a new version being dropped early next week: https://getgophish.com.

Everyone should have access to training to prevent this as much as possible.
> As for J.S. Mill, you might be surprised; he wrote that:

As far as J.S. Mill's economics works go I've only read his "Principles of Political Economy", so he might have had other beliefs later or earlier in his intellectual career, I agree. I'm too lazy to look for the exact quote, but I found a pretty good round-up of what I remember of having read in here (http://www.econlib.org/library/Essays/LtrLbrty/gryMTR2.html):

> Mill's remedy for this maldistribution, which he proposed in the first edition (1848) of the Principles, was the institution, not of an estates duty, but of what we would nowadays call an accessions or inheritance tax, to be levied on the recipient and not on the donor of capital. For Mill, the merit of such a tax was that, unlike other arrangements, it need not transfer wealth from private individuals to the state, since it was easily avoidable by the desirable expedient of dispersing one's wealth widely. Importantly, Mill favored a steeply progressive inheritance tax. This tax, though it would allow the transfer of a "modest competence," would destroy all great fortunes in a couple of generations.