skysight-inc/HackerNews huggingface dataset:
I'm really leery of this recent push towards trying to create "acceptance" around autism. Yes, some people are only mildly autistic and can live mostly normal lives with significant extra help. If my luck holds, my autistic son will fit into that category.

But autism is also the completely non-verbal 12-year-old I recently encountered at an indoor play structure, whose only verbal communication was the characteristic autistic squawk (I've heard it from my son too, and quite a few other of the autistic kids we've met through various groups), and who only narrowly avoided scratching his mother when she tried to remove his empty milk cup by virtue of her having long practice at dodging his clumsy movements. (I don't think he was deliberately trying to hurt her, but that matters little once the hands get moving.)

I'll also be blunt, because I think too many people dance around this issue out of fear... even parenting a mildly autistic child is unbelievably emotionally exhausting. A great deal of those human interactions that are part of the reason to have children, or, if you find that too, ah, direct, one of the major things that helps you get through all the difficult work at 3am and during toilet training and all those other times... gone. I was actually creeped out a bit when holding another parent's baby a few months ago, because their five-month old was making eye contact with me... an experience I am not used to. (My other kid can't either, but for other reasons.) That's what I'm used to. It's hard to even express until you're in the middle of it, but it's hard.

Honestly, improving autism isn't all about just the autistic person's life; they don't live isolated lives, in fact, they're drawing more than average resources, emotional and otherwise, from those around them. Those who live around the autistic person could benefit from autism being improved.

And I'm grateful for what research has been done that has in fact been helpful. Never in a hundred years of parenting would I have imagined the amazing transformation that can come over my kid just by strapping 2 pounds of workout weights to his legs... I never would have made the proprioception connection without the research that has been done on the topic. So you'll forgive me if I get a bit nervous about anything that makes it even REMOTELY sound like maybe we should just shut down all the research and "accept". My son may need emotional acceptance, but he doesn't need acceptance of his autism... he needs research on how to deal with it, and parents who do not simply let him retreat into his own little world and pull the entrance in after him, something he clearly wanted to do when he was 3 and 4, thinking it's just another choice.

Do not stop the research. Do not just "accept" autism. If your experience with autism leads you to the conclusion that's a valid choice, then be grateful you were only grazed by the bullet. Not everybody was, and that may even include some people around you who were only indirectly affected.
"It make take a few iterations of the source code with the help of other users to make it fully portable "out of the box.""

Need any help with porting to Net/Free/OpenBSD?
It's not about coolness/hipster, really. Though the recent surge in popularity certainly could be explained that way.

I agree that the taste takes some getting used to. There's a reason the unofficial slogan is "Man gewöhnt sich d'ran" ("One gets used to it"). For me it's mostly the high caffeine content alongside a comparatively low sugar content (lower than any other energy drinks or other caffeinated soft drinks I've come across -- except for the "sugar free" ones).

I tried sugar-free energy drinks for a while but I find the taste too jarring to get used to. I still drink sugar-free Red Bull on occasion (and actually prefer it to regular Red Bull) but I couldn't stand relying on it as my primary source of caffeine.

Basically, Club Mate is my coffee. Red Bull is my espresso. I don't drink coffee (I can't stand the small) but I think that comparison probably works best.

EDIT: Just noticed the article says the slogan "Man gewöhnt sich d'ran" is on the bottle. That seems wrong. I've never seen the slogan used officially. I always thought it was coined by its users, not the company itself.
> we need the US to catch up with Europe

Europe is on a path to technological stagnation and demographic collapse. There's a reason its economy is depressed, its electricity fantastically expensive, its people angry, its programmer wages depressed, and its startup scene anemic.

Europeans refuse to embrace modern technology like genetic modification and nuclear power, much less allow the flourishing of information technology. They'd rather comfort themselves with their pseudoscience and their precautionary principle and their Luddite privacy regulations than join the rest of world in imagining something better.

Europe is absolutely no model to emulate.
There have been experiments along these lines. I'm not sure why but I read about this on on HN not so long ago..

https://news.ycombinator.com/item?id=8792192
Looks like I cant reply to you due to comment depth, so I'll reply here.

The reason for being able to push "breaking" changes into the codebase is for future consumption. We control the consumers, which verify that they are able to integrate.

When all consumers have had their contracts updated to be insync with that service, then that service is no longer breaking - even though it hasn't been changed.

Its basically a way of preventing inter-service blockers.

I must admit, I thought these kind of pipelines would have been a lot more commonplace than they appear to be.
Agreed. STEM has proved incalculably valuable in servicing the lowest (most essential) tiers of Maslow's pyramid, but the higher ones (love through to self-actualization) require more nuanced investigation. As society progresses, people worry less about these tiers, like hunger, and it's not unlikely that the primary concerns of future generations will be emotional/social.
It's an interesting thing nodejs. I think there is also another advantage which is the sheer number of Front End devs who can now do backend work.

Showing my ignorance a bit here but why is it insane for security reasons?
I don't see that... or rather, if it's true here it's true to a significantly greater extent in most other industries.

Money continues to be available, and often lots of it. It's available on better terms than most others in most other professions can even imagine receiving.

To put it bluntly: in most industries you are meat and own nothing and never have any chance of owning anything. This has been the condition for nearly all human beings who have ever lived, today and in the past.

There are also more alternatives to VC today: larger angel rounds, crowd funding, etc. It's also easier to bootstrap since everything (but people) has fallen in price. Those two things together have made the funding environment more competitive for VCs -- they have to offer more value or compete at the higher end.
This is a great move and has inspired me to think of how I can do this for the sites I run.

The problem I have is that I run forums which accept user generated content, and the links in the content are then parsed and embeds are put in.

For example, YouTube links have the embedded video put below to the link.

YouTube support https, but a lot of smaller sites that offer really useful tools don't yet support https. An example is something like http://www.bikely.com which does not support https at all, and yet the embedded maps are common enough on the cycling forums I run.

I cannot just proxy via a https domain as these sites usually have JavaScript that require permission to talk to their own domains.

I've decided to start emailing all of the 3rd parties to ask that they add https to their site.

Almost 40% of my traffic is now over https, and it's harder to increase that as every time I try to I receive support complaints about mixed-content warnings, missing content, etc.

If you also run a site that has embeds in user generated content, please consider emailing the 3rd parties and explaining why they should move to https.

There are only a few things holding back a lot of sites and it's no longer the cost of a cert and SSL termination:

1) Embedded widgets that are http only today

2) Advert widgets/scripts that are http only today

Those things hold the vast majority of news sites back too. I even checked the Guardian yesterday and no https available. The only news site that was https was The Verge, but I'm not sure tech news is really news.
I'm going to second this. I loved the slider and shades rather than a specific number. It gave me a way to guage where I felt like I was. I also liked that there was a description to say, hey this is what a 10 really is, don't just give a 10 because you want your job to be exceptional. In my case it helped me be more honest with myself (I'm a habitual 10 or 1 guy.
> "In short, the microservice architectural style is an
> approach to developing a single application as a suite
> of small services"

Sure, it's a single application from the perspective of the user, and that's a great abstraction to keep in mind when you're talking about things like uptime. But from the perspective of the operator, it's purely an abstraction -- a name you give to the collection of things you're manipulating.

As such, I'm not sure building a single repo of git submodules makes much sense. Maybe for accountability reasons, but not for actual operations. The ·raison d'être· of microservices is to decouple the lifecycle of each service totally. By recombining them into a tagged release repo, you're arguably subverting that intent.

> The problems occur when you have multiple commits to
> different services. If a build is marked "red" because
> it fails a "future integration" then it just means that
> it is failing at that point in time. It may, following a
> commit of a dependency, become valid. However, it would
> need to have its build manually retriggered . . .

Yep. To solve this problem, your CD system needs to automatically trigger rebuilds (and re-tests) of dependent (downstream) services when a dependency (upstream) changes. The easiest way to do that, in my experience, is to have a manifest in every repo that specifies dependencies as a flat list, which the CD system can parse to build a dependency graph.

Tangential point, but -- with this, we're just scratching the surface of the incidental complexity that comes when you move to a microservices architecture. This is the stuff that isn't in all of those exalting blog posts -- beware! :)
It's not at all contradicted by the document. The document references Section 702 of the FISA Amendment Act, and the Stored Communications Act. Section 702 allows targeted access to non-U.S. persons and Section 2703 of the Stored Communications Act allows the government to compel disclosure of stored communications with a warrant, or notice to the customer plus a subpoena or court order. 18 U.S.C. 2703(b)(1).

Nothing about the document suggests blanket or direct access.
don't understand why they keep saying it's a VC in the article. It's a startup accelerator
The software would only be a small part of this project. The issues they discussed in the clip (risk of sudden failure, radio interference) were hardware issues.
Reminds me a lot of Happiness Metric: https://www.happinessmetric.com/ I used them for a long time.
I would imagine that were this published in 2007, he would also include shoes with actuators in them that are constantly working to alter your gait; perhaps something that also affects how you move your hips or arms, although I'm not sure how this could be done.

https://en.wikipedia.org/wiki/Gait_analysis
I'll go on record as saying I think the slider is a good idea. It's the subtle difference between picking from a pre-defined list at once versus exploring your feelings sequentially that makes it valuable. If as the weeks go on they change the wording so you don't always remember the answers it can be a way to consider each option without a bias towards another choice. If you see all options at once, you immediately compare them, if you view them sequentially you consider each one more independently. Perhaps this is a pointless distinction for some (and for some personalities I'm sure it is), but to me it's valuable to take time and process and explore my feelings, rather than choose as quickly as possible.
You answered that one yourself :) Deprecation means to publicly notify that some API endpoint has hit end-of-life, and that a better alternative is available. If you completely rewrite a service, it's your responsibility to implement the same interface that you had before on top of it. Then you deprecate it and also publish your new api or data schema. Once you get around to migrating the rest of your application's services away from the deprecated endpoints, the next version of the microservice in question can remove that old code entirely.

Imagine Twitter or AWS completely rewriting their backend -- if they were to announce to the public that at a specific time, their old API URLs would 404 and the new ones would go live, it would be a wreck. They'd support the old API through deprecated methods and tell users they have X months to migrate away, if they remove that layer at all. Stress-free SOA must employ that same level of discipline in order to stay stress-free.

--And, functionally, the much easier alternative here isn't to re-implement your old API on top of your ground-up rewritten shiny new service, it would be to reduce your old service to an API shell and proxy any requests to the new service in the new format. Far less work that way. Use more traditional API versioning for the much more common updates. Unless you're rewriting your services every other week, in which case you have an entirely different problem ;-)
Excuse me Mr Lol, but since it happened, it would appear that it in fact is how the internet works.

If the postal service misdelivers some mail are there criminal charges?

I would suggest resisting the urge to hit every problem and mistake in the world with the law hammer; it is rarely productive, and generally isn't how the world works.
When asked what it tastes like I generally say "like drinking Bionade[0] from an ashtray". I can't justify why I like it, really.

[0]: https://en.wikipedia.org/wiki/Bionade
It would be awesome if this had a feature for you to group employees together, or to say what company you worked for.

I'd love to see how my entire team feels on a week over week chart. It should be anonymous to the employer, but it'd be cool to see the stats. But I'm a chart nerd.
Seedcamp is "€25k for 5% w/ optional further €50k for no more than 2% (totalling €75k for 7%)" [0], which at current exchange rates is around £18K for 5%.

[0] http://seedcamp.com/our-deal-terms/
100mg of Caffeine? I tried a couple of cans of Jolt Cola back in the day, and with it's (then) 71mg of Caffeine I thought my brain was going to pop out of my skull. No idea how the drinkers of Club-Mate don't have health problems from this.
Rob Pike: Go in Go [video]
> Today, we can get away with ‘knowing’ how Google works without understanding what a ‘principal eigenvector’ is. Tomorrow, we need to absolutely know that.

Part of the advancement of technology is that fewer and fewer people actually understand how stuff works. What percentage of the population has any notion of how a computer works under the hood? How many people understand how our national power grid works? Our sewage system? Our cars? As our world gets more sophisticated, we specialize; we have to. Sure, there will be people who will have to know about eigenvectors tomorrow - but do we all? Not by a long shot.
Not overall. There may be a bubble in certain small areas of tech, but there is nothing happening right now that equals the mania of the late 1990s.

I was there, and nope. Totally different economy and culture. To have a bubble like that you need optimism, and I have never in my lifetime seen a greater sense of hopelessness and pessimism and anger. Outside of coastal alpha cities like SF, NYC, Boston, LA, etc., the mega-recession of 2008 onward did not end. There is no hope, no opportunity, and everything is rising but wages. I've spoken to people who were older in the 70s and early 80s and some have compared it to then, but I have a friend who remembers the 70s well and he insists this is worse.

We may be in a sort of bubble, but it's not centered on tech or specific to tech. We are at a time in history where unprecedented amounts of money are sloshing around at the top and it isn't 'trickling down' much via ordinary routes like wages. As a result, there is perhaps something like a bubble in the sorts of assets that kind of wealth imbalance inflates: real estate, bonds, stocks, and yes perhaps other forms of investments rich people buy like private equity.

If there's a bubble in angel or VC activity, it's a shadow of that larger imbalance rather than something centered on tech in particular. There's a ridiculous amount of money at the top that doesn't know where to go, and some of that is going to be available to inflate startup valuations among many other things.
PostgreSQL has great language features and has been a stable OLAP platform. Coming from MSSQL, the only feature I miss is query parallelism.

The lack of equivalent feature in MySQL makes it difficult to work with once accustomed to others (OLAP context, not OLTP).
What about server-side render on page fetch and client side rendering afterwards? Or running business logic client side so the UI appears snappy and then enforcing that logic server-side? This would benefit from the same code running in both contexts. But I agree with your other points, its not a huge deal. Even the points I mention don't seem like core issues.
Very interesting tidbit about the 10x number of FB shares. I sometimes wondered why FB keeps showing me so many news on sites outside of FB, sending me away from their site. But I guess they don't send away quite as many people as I assumed.
Or simply:

git add ...
git commit --fixup $SHA
git rebase -i --autosquash --autostash $SHA~
I admire Martin Fowler as well but he is so wrong here.

Microservices should be designed, developed and deployed as 100% autonomous entities. The whole point of them is that you can reuse individual services for new applications or integrate them with third party (e.g. different team in your company) services without affecting other applications. Otherwise what is the point of doing this ?

Using git submodules absolutely violates this and is a bad idea. I would have separate repos and deploy scripts and then set the version number of each service to the build number which guarantees traceability and makes it easier for change management.
agree on 1 and 3.

As for 2, I think it makes sense. You can pre-render your GUI on the server side, so that clients get served proper html rather than an empty pile of js, and then have the same codebase take over on the client side, single-page-app style, just talking to the backend to fetch data.
Only if DB runs JS. ;)
Have you got some sources for this? If you've got criminal gangs willing to cut people's fingers off for their money, why do they bother instead of doing something easier and more reliable? The threat of having your fingers cut off would, I expect, be all that's needed to get people to hand over their cash. Sure, not everyone has got cash on them right now, but not everyone has got an ATM card on them and not everyone has got any money in their bank account. Additionally, they seem to be not fingerprint scanners, but vein pattern scanners, and the manufacturers seem to say that a finger no longer attached to a body won't be accepted.

If you're willing to cut people's fingers off and then walk to the ATM, you'd be willing to simply rob people in some other much easier and much more reliable way.

It seems that about a year ago someone was considering such ATMs [1]. Are you sure this isn't just the fears of people (as mentioned in the article) blown into urban legend?

[1] http://www.news24.com/Technology/News/Fingerprint-ATMs-Will-...
I microwave my clothes.
Especially in light of the cost of "updating" it. I realize it's not the $2M to replace an amiga.
Dev Jargon Explained in Human: 5 Most Common Misconceptions
EcoHealth Alliance (EHA) Is Hiring a Software Developer
EHA is seeking software developers for our data science & research technology program. The focus of this position will be to develop global health web platforms that are actively used to monitor global Emerging Infectious Diseases & contribute to the analysis of disease emergence. Duties include: developing natural language processing (NLP) & machine learning systems; contributing to open source software; mobile app development, building front-end(s) for web frameworks (e.g., Meteor); designing scientific visualizations; data & text mining; geo-tagging & geo-visualization; network modeling; contributing to technical project management; & some collaborative proposal development. We mostly code in CoffeeScript, JavaScript, & Python, use Meteor for web apps & AWS for hosting. You will be expected to contribute to our code management & distributed version control practices, & to adopt our web-based project management tools. We are interested in hearing from candidates with experience & interest in working on both the front- & back-end, & experience with other languages is fine with a willingness to branch out into our stack. This is a temporary 1yr position with the possibility of being extended to 2yrs. Excellent employees will be converted to permanent staff. EHA offers a competitive salary & a comprehensive benefit package. EHA is an equal opportunity employer. To apply, you must send your resume & a personalized cover letter as one document to dev-jobs@ecohealthalliance.org with the subject of "Software Developer 2015". Applications without cover letters will not be evaluated. This cover letter will help us assess your ability to communicate effectively & will be used as the primary mechanism to determine whether a candidate is asked to interview for the vacant position. In your cover letter, please briefly describe your past experience with web development frameworks, machine learning, NLP & public health.
I've seen enough code to know that if it's in an example, it's in production.
Welcome to West Michigan local media (though I'm sure this phenomenon isn't unique to this area). While it can probably be explained by bad writing, they've also learned that anything that provokes the ire of tea-partiers is golden for driving pageviews.
Very well presented and interesting analysis.

Primary compliments I also have in particular for the author is inclusion of a link to source code and the concise but complete and informative "tools used section" describing the process. I wish more analysis (particularly those presented on more reputable news outlets) was presented with a similar section for reproducibility and exposure to analysis techniques.
Generators are still fairly rare in the suburbs. Load shedding has been in SA for several years now.
"However we're living in a time when absolute right to privacy and anonymity in public no longer exists..."

And that is the crux of the issue. It needs to be made a right and enforced like every other right. The problem is that it isn't and it is like the wild west when it comes to people's privacy and data. Given the rapid rise of big data and the surveillance state I would say that a time of flux is just starting. My sincere hope is that it ends with strengthened rights for the individual. I am not convinced it will, however.
Google has a couple good starting points:
http://www.enterprisenetworkingplanet.com/netsp/article.php/...
http://blog.pluralsight.com/bgp-border-gateway-protocol