skysight-inc/HackerNews huggingface dataset:
> From the NSA’s perspective, having the keys to the backdoor is an asset, but having a backdoor at all is a huge liability, now they’re not the only game in town. US businesses and citizens simply have more to lose. Honestly, I think it’s laziness and inertia more than conspiracy.

You're assuming (fully) rational actors. It's fairly easy to have blindspots when they are (at least temporarily) useful.
How to alert, debug / troubleshoot, and fix Kubernetes CrashLoopBackOff events
A huge upside of Windows 10's six month rolling releases is that they initially broke a lot of badly written things, and software and processes have had to improve to handle them better.

The end result two years later is OS upgrades rarely break much, and regular updates never do. Enterprises can be unstuck but it can be painful.

I think enterprises are still shifting from the old approach where you make it work and then it's fine, to realizing that in an internet-connected world, you have to keep up at all times. A few big liability cases would do wonders to push this shift along.
> If the salary for each person was X, I asked for a salary bump of 3X [and they didn't]. ... And from that point on, I stopped treating my job as an extension of my identity or fulfillment of purpose.

Indeed, the best work is done when you do it for yourself. People basically sign their brains away when they go to work for Facebook and Google. Those companies will be likely to get B players no matter how many seemingly great people they hire. The 4.0 MIT grad who can recite chapters from his CS401 class isn't necessarily an A player. Most of the A players I know are either ex-Facebook/ex-Google or turned down working at those places because they have more important things to do with their time.

The real A players are much harder to find and are much harder to value. Without ownership in what you do, there is a high probability that you will not be at your best. If you need to be paid to do something, it is unlikely to be what fulfills you.
> This article really highlights how odd our methods of valuing output are. Ultimately if someone is idling for 6 years because they've written a program to do their job for them, who cares? They are delivering the same output which hopefully the company deemed was valued at X amount BECAUSE it delivers Y amount of profit/returns.

Their boss cares. This is capitalism, and capitalist ethics say you should be fired if you're idling and not continuing to actively labor for the boss anymore. She's not getting anything in return for your salary. You more than likely signed away all rights to the fruits of your labor when you took the job. That means "your" automation is really your boss's capital, and you have no rights to be perpetually compensated for it.

So, if you ever automate your own job, don't tell anyone. Also make sure to make your automation so arcane and impenetrable that no one else can hope to use it.
It sounds a lot like TBL’s Solid with a blockchain tacked on.
Windows 10 October 2018 Update is available now
C++ Telltales Pt.6: The Mapleton Pattern
You don't need EKS. Just use kops to build your cluster on plain EC2 instances.
Literate raytracer: a simple implementation of raytracing in Javascript
You can run Kubernetes on AWS without EKS and if you use t2.micro instances it would be around $28 per month if you use the load balancing technique here (where it is DNS based on an actual LB). $21 a month if you account for the free tier (and this article uses Google's free tier).

If you further use spot instances (the equivalent here to "preemptible") you can save a ton more.

The real savings (or $7 per month) is that on GCE you won't need to run your control server. GCE does that for you for free.

Edit: now another issue here is (and I have no idea if this is true for GCE like it is AWS). t2 instances will throttle you if you use too much CPU which can be an issue when running a lot of containers.
You’re not rebutting the parent comment. I’ve built tools in this space. The bar for “insanely good” is very high, and the market size is quite small.

It’s a crappy business from an investor perspective, and legions of nerds have washed up on this particular beachhead.
> Trade unions, which have closely aligned themselves with Gov. Andrew M. Cuomo and other politicians, have secured deals requiring underground construction work to be staffed by as many as four times more laborers than elsewhere in the world, documents show.

> The critics pointed to several unusual provisions in the labor agreements. One part of Local 147’s deal entitles the union to $450,000 for each tunnel-boring machine used. That is to make up for job losses from “technological advancement,” even though the equipment has been standard for decades.

...and so forth. https://www.nytimes.com/2017/12/28/nyregion/new-york-subway-...
Tower Web – A fast, boilerplate free, web framework for Rust
Tesla is facing the prospect of needing to sell a honking load of stock at a discount to deal with their debt, and to do that they need a high stock price. While Musk appears to be a liability in many areas, he is the focus for a cult of personality that has made Tesla what it is, and has shown incredible talent for inflating the price of Tesla’s stock on that basis.

So while Tesla as a healthy company without crushing impending debt would almost certainly be better off without him, Tesla as it is only really exits because of his presence. Long term they have to actually make a lot of money and stop hemorrhaging money, and get out of their death spiral. Short term the only way to do that is sell expensive stock, and that stock is expensive because of the cult of Musk.
Z-LAB Report – Analyzing the #GandCrab v5 #ransomware
Do you have any resources for the same? I learnt the basics from the Book of Shaders and other tutorials but can't seem to find find any advanced lessons.
When picking preemptive machines for this demo project is the intention here to simply save money for a pet project?

I guess my main question is would anybody actually use preemptive for k8s knowing that if a worker node gets reaped k8s will magically route only to healthy nodes while the preempted instance replacement is standing up?
In the first fire-engines[1], a boy was constantly employed to open and shut alternately the communication between the boiler and the cylinder, according as the piston either ascended or descended. One of those boys, who loved to play with his companions, observed that, by tying a string from the handle of the valve which opened this communication to another part of the machine, the valve would open and shut without his assistance, and leave him at liberty to divert himself with his playfellows. One of the greatest improvements that has been made upon this machine, since it was first invented, was in this manner the discovery of a boy who wanted to save his own labour.

-- Adam Smith, Wealth of Nations

https://en.wikisource.org/wiki/The_Wealth_of_Nations/Book_I/...

1. The modern term for these devices is the perhaps more familiar "steam engine'.
That was probably referencing the story of the origin of the IBM PC. This anecdote was given as the reason they got the green light to develop the PC in Boca Raton independent of the rest of IBM.
This reminds me of an article on The Verge two years ago documenting the semi-intentional convergence of interior design [1]. Admittedly, there was a focus on spaces like short term rentals and coffee shops, but the effect seems translatable; we seem to be converging on sterile, "personalized but not personal" designs.

I'm curious if, similar to the dislike many have for the unrealistic airbrushed images of the human form, we will arrive at a place where these sterile, fatastical spaces are no longer in vogue. In many ways, it encourages a similar level of unhealthy pursuit of the unattainable.

[1] https://www.theverge.com/2016/8/3/12325104/airbnb-aesthetic-...
Services that don't have options besides Facebook/Google are the best of the bunch.
For me the #1 reason why they are slow is because everything requires consensus or maybe another way of putting it it's hard for people to make a decision on their own.

Let's say I want to change some part of the UI of some app. If I'm by myself I just change it. If I'm on a team first I have to convince whoever has the power to decide to change it to allow it to be changed, that might even be a whole committee. Then several people will be involved, likely a UX designer, possible a separate UI designer, all of which will have to discuss the feature and all of which also have other responsibilities.

The larger the company the worse this usually gets. Maybe the change has to be run by the security team to make sure the new UI is not a security issue. Maybe it has to run by the privacy team to make sure it's not going to leak data. Maybe it has to be run by an inclusivity team to make sure it's not offensive in some culture I'm not familiar with. Maybe it has to be run by a localization team to make sure it will work in every language.

All of those things add time. Maybe they are all required and good, especially at a large company with a global marketplace but they certainly add to the time taken to do something that a tiny team wouldn't do.
I disagree. There are gradients to the type of engineer you are and the type of employer you have (or are, in the case of the HN crowd), how much you make/raise, etc.
I'm going to push back against this narrative, because it seems a lot of the "let Elon be Elon" arguments are neatly encapsulated in this line:

Tesla is doing wild things which are causing crazy growth, but also crazy panic.

But the critics of Musk's behavior would respond, I think correctly, that there is a categorical difference between "wild things which cause crazy panic because they are high risk with high upside potential ('crazy growth')" and "wild things which cause crazy panic because they are high risk with little to no upside potential." And while perhaps sometimes it's difficult to tell whether a certain Crazy Elon Thing falls into Category A or Category B, things like "let's accuse someone who criticized me of being a pedophile, that'll teach him" or "hey, we have nothing signed and this blatantly violates SEC rules, but screw it, it'd be funny if I said we were going private at $420 a share, because 420"? Those are very clearly things that are in the "little to no upside potential" category.
If Elon has threatened his board, then they need to fire him, or resign themselves.
From the article:

>But at this moment, a sign-on service by Google or Microsoft has one big advantage over Facebook’s: Those companies did not lose control of 50 million people’s accounts, and Facebook did.
I was expecting an ML-driven framework where you write the HTML you want to scrape, and the framework diffs the trees and attempts to extract the information from the target tree as best it can to match your input tree. That's what pops into mind when I think of "declarative" scraping.

LET google = DOCUMENT("https://www.google.com/", true)

INPUT(google, 'input[name="q"]', "ferret")
CLICK(google, 'input[name="btnK"]')
WAIT_NAVIGATION(google)
LET result = (
FOR result IN ELEMENTS(google, '.g')
RETURN {
title: ELEMENT(result, 'h3 > a'),
description: ELEMENT(result, '.st'),
url: ELEMENT(result, 'cite')
}
)
RETURN (
FOR page IN result
FILTER page.title != NONE
RETURN page
)

Looks an awful lot like:

const { document, input, elements, waitNavigation } = require("your-library")
const scrape = () => {
let google = document("...", true)
input(google, "...", "...")
click(google, "...")
waitNavigation(google)
return elements(google, ".g")
.map(r => {...})
.filter(p => {..})
}
scrape();

Am I missing something here? I don't see anything declarative about the the first one over the second; both of these look identical and rather imperative to me. Is "declarative" becoming a buzzword (thanks to React, maybe?), or am I missing something?
I think this one is mostly reflective of the risk/reward payoffs of aggressive and unusual play in any particular game. Play to win means - force the confrontation, take gambles, push your way into a surprise advantage. Play to not lose means - lean on your techniques, stay in control of the situation, build an advantage gradually.

And for most games, most of the time, playing to not lose is a more reliable way to win, because it is more consistently rewarding to practice, even though it can result in a boring risk-assessed playstyle. Playing to win is an emotionally-driven way to do things and good technique will usually counter it, but every once in a while, late in a match, the mask slips and there's an opportunity to make a play on an overwhelmed opponent.
> These articles about Elon are interesting to me because Tesla could not have become such a valuable car company in such a short time if it wasn't for Elon, and that includes his personality.

> Yet, many couch investors would prefer to have a CEO who is stable, boring and predictable. People want to put their money in for steady long-term returns, and not worry

A much simpler explanation, lacking the conflict, would be that early, start-up hungry investors prefer the rockstar CEO, and long-term investors would prefer a business-seasoned CEO.

To which I would say: Tesla has been around for 15 years (longer than Facebook!), and as the fans frequently profess, its market capitalization has (in the recent past) already surpassed that of other established car manufacturers. Perhaps it's time to leave the startup image behind.
Is there anywhere I can get a list of all the websites I've ever used my Facebook account to log in to? I know I've done it for some of them in the past, but I don't remember which, and if any of them are still websites that I might use, I want to switch them off Facebook login so I can finally delete my account (which I don't use for anything else).
Same here on ubuntu with xfce. They should at least overlay something before going to sleep as a quick fix.
> Well, even if we assume you're right, the Japanese certainly don't have a monopoly on ethically questionable relationships with animals

You're right, they don't. But the American head of state isn't a marine biologist (or any other kind of scientist) either.
In the effort of simple counter proof: you can dig a hole with a spoon.

That requires a substantial amount of hard work but unlikely results in a measurable amount of success. Certainly one less than would be if the proper tools were used.

And I do agree with you that it is not the only factor. But this is why I differentiate cause and correlation. And the disagreement is likely to how we are using those terms. I am using "cause" in the colloquial sense (because context from above) of how most people do not see multivariate equations, but single factor (which is an unfortunate thing) ie. "cause and effect" (but we both know better). I am using "correlation" in the more rigorous manner meaning "related to; a statistical variable; or to be in association with".

And going back to your RL example, I think you mention one part which proves my point as well.

> the exploration/exploitation strategy

You may notice that many learning algorithms have a substantial amount of failure. After all, it is the failure that leads to success. BUT a key point is that it is not the effort put into the attempt that led to success, it is the adaptation of a new strategy after recognizing the failure. You could just as easily never visited that attempt method and thus your efforts would lead to a higher success/work factor. You could also never change strategies and your efforts would result in a substantially lower success/work factor. More explicitly "hard work" is a variable that is coupled with "strategy", and the value of "hard work" can be astronomically high but the value for success can be zero. And for this reason we say it is not "the cause" but rather "a factor" or "correlates with".

Also, as mentioned in a grandchild to my post, this is a saying which I gladly will admit does not cover the entire scope of what factors lead to success. Even the unpacking of implicit information cannot do that, as a full description of the path to success is rather cumbersome.
They don’t care
The name fastai sounds suspicious. There is "fast" and "AI" in it, so I fear that it makes the easy things easier and the hard things harder. It just sounds like too much fluff. We obviously don't have AI yet (but pretty convincing machine learning models) and we won't get it in the next years (not fast) - so if software, a company or an organization puts "ai" in its name (or chooses it as top-level domain) I suspect they just want to ride the hype train and am very skeptical ...

@Topic: What is the difference to Keras, PyTorch, etc.? They are already pretty high-level and the basic models for common tasks are available in all libraries at that point.
If you are into big history science fiction, I highly recommend "The Wandering Earth"[1] by Liu Cixin, which explores this theme (sort of). Short enough to read in a night.

[1]: https://www.goodreads.com/book/show/13554058-the-wandering-e...
@jph00 where do I find lstm/gru/seq2seq layers for time-series sequence predictions (not text)? Also interested in autoencoder implementations. The fast.ai docs search does not really work for this. What do you think about other notable APIs built on top of pytorch such as Pyro and AllenNLP?
Although I kinda love the idea of desperate notes and documents, I think you probably meant "disparate."
warp – A super-easy, composable, web server framework for warp speeds
That's a nice thought, but do you have any evidence to back this up?

The notion that religious people are less likely to do bad things is highly problematic, objectively and logically - and it carries the unfortunate assumption that non-religious people are more likely to do bad things.

People should not need to subscribe to a paranormal belief system to understand that theft, rape and murder are bad.
Now look at it from the employees perspective; None of these cases result in the person who did the automation from gaining additional compensation and half of them result in them loosing their job.
Uh, yeah, ok.
Full disclosure - I work for Tyk :)

One of our users recently did a write up on their experience using us with particular focus on plugins: https://bitsofinfo.wordpress.com/2018/06/28/migrating-to-tyk...

Author: https://github.com/bitsofinfo
Javascript isn't in uppercase, therefore it is an inferior language to write queries in. The best, most concise solution here is to reinvent javascript in uppercase, then pass it off as a new QL.
Settings > Apps and Websites > Expired
Is ~15 dollars an hour considered good? It seems pretty high from a European perspective. In my country, minimum wage is about 10 eur/hour, and 15 eur/hour is normal for a junior developer.
Let me guess. Did you just been triggered by the $2 a week diet thing? Then don't be, I'm actually not very proud of it.

I did it from time to time for about few weeks so I can quickly lose my belly fat. And I don't like it at all let alone recommending it.

> the most useful metric I know of to look at is the affordability ratio

Of course. I just searched a bit, the DPI seems to be ￥7,815 or $1,137 for the first quarter.

However, I don't have any information other than that, and dig the information needed is too hard for me :(
they are less than 0.3, not 3.
EKS is indeed expensive. I started creating https://github.com/cloudboss/keights for automating Kubernetes stacks before EKS was a thing, but I still prefer it over EKS. You can use it to set up a cluster using plain CloudFormation, or with an Ansible role which wraps the CloudFormation stack.
Noise Sensor Voice App
I'm beginning to think that what Kubernetes needs by far, is a better development environment story.

1. Something that makes it easy to run the application(s) you're working on locally...
2. ...but have it interact with services in a local kubernetes cluster easily.
3. Something that makes your entire development environment effectively immutable, read-from-files the same way as the immutable infrastructure we're talking so much about.
4. Something that gives you a good start to running in production, so the first day of bringing your service up isn't a mess of trying to find/remember what environment variables/config options to set.
5. Something that's one tool, instead of a mixture of `minikube`, `kubectl`, `docker`, `draft`, and `telepresence`.
6. Something that's opinionated, and follows "convention over configuration", with conventions that make for the best future designs.

Basically, we need something with a Rails-like impact but in the Kubernetes ecosystem.
Ok, maybe I was spoiled with 100 Mbps connection at the time but I was mainly talking about Apps. They were not web-based, all written in C, some form of BASIC or Assembler.
The USA has decided 3 times to create a middle class. By enacting massive transfers of wealth. Most recently the New Deal.

Wealth and Democracy: A Political History of the American Rich
by Kevin Phillips http://a.co/d/glFxd7G

That the rich get richer is just math. Without deliberate wealth redistribution, growing inequity is inevitable.

Gross inequity and democracy are incompatible. A democratic society must balance capitalism and socialism to survive.
> Just look at the results. If labor rights were increasing they'd be able to pull more compensation due to a better negotiating position, but real wages are falling.

That's just assuming the causation goes the other way again. If the labor rules instead are pricing smaller businesses out of the market leading to business consolidation that gives capital more power over labor, you would expect just what we see.

It also doesn't make a lot of sense to expect a lot of labor laws to increase wages regardless. If you pass a law requiring maternity/paternity leave, that benefits the employee but raises costs for the employer who has to find and pay a temporary replacement. The expected result of that is to suppress wages rather than increase them -- the money has to come from somewhere and most businesses don't have huge margins.
I mean, he said it outright: “I think you'll find that most people who 'keep the wallet' are probably not religious...”

I don’t think it’s so much a carried or implied assumption as his central thesis, and his justification down the thread is a page of more claims and anecdotes. Call me cynical, but I don’t think there is any “there” there.
I think it's a little more subtle than that.

In the context of a startup, if you try something and fail, you'll generally be recognized for taking initiative even if the result does not pan out. At that level, learning what doesn't work is often as valuable as learning what does work. Startups often bias towards hiring people with just this mentality because that is what they actually need.

In the context of an established company, sticking your neck out is like career suicide unless it's a sure thing. Unlike a startup, you're risking an _established_ reputation on a new idea. So you end up working in an organization that has an inherently different view of risk and trying new things.

I'm not sure whether "nobody knows how to do anything" results from an institutional aversion to risk or from the natural result of hiring people that fit within that system, but the end effect is exactly as you describe. It's way too hard to do anything off of the beaten path, and trying to do anything along those lines _immediately_ results in negative feedback which makes employees a lot less likely to attempt such actions in the future.
I also hope they have severe penalties for dumping trash near the nearest river or bush. Because this is what I still see happening in my country, especially on the countryside.