skysight-inc/HackerNews huggingface dataset:
Our cloud service here at confluent is designed around giving customers their own infrastructure. A lot of the times, that means giving them their own k8s cluster. The management overhead there isn't the issue however.

The real issue comes into play when you try to make developer environments.

To give our developers any semblance of a "real production-like" workload, they need to work with an entire kubernetes cluster - maybe even a couple - to simulate what's happening in production.

This means at any given time, we have hundreds of GKE clusters because each developer needs a place to try things. Yes, these are ephemeral and can be tossed aside, and yes they cost a tiny bit in VM prices, but adding a per-cluster management fee is going to skyrocket this expense and push us towards trying to figure out ways to share these clusters between developers, which defeats the entire purpose of the project.

We'll have to seriously consider abandoning GKE for this use-case now and that sucks, because it's by far the fastest managed k8s solution we've found so far.
Of course it didn't, look at my sibling comment for a link to the updated doc.
I would think the open sewers and horse dung (and dead horses) would be much worse than the heat.
Also, every 10th truck probably has a guy with a shotgun in the back.

More to the point, I think if we're trying to secure the use case of "truck the same as it has been for 30 years gets a black box put in it" we're doing it wrong. After not too long you just flat out won't be able to get in, even if you do stop the truck from moving. You won't be able to drive it anywhere - what need is there for a cab on an auto-truck?
I don't know. I feel like I've always needed to think about any line of code with several operators on the same line, but I've been in this business for a long time, so I might have learned the habit from negative experience.

I'm glad you mentioned it though, because now I'm curious if there's a difference among programmers who score well or poorly on a cognitive reflection test. Maybe people with a tendency to suppress their intuitive response are also less likely to think that a line of code has an obvious meaning?
How about a straightforward response, rather than trying to change the subject again?

What's more, I've seen this interview multiple times. Listening to Gosling stutter and be coy is not illuminating in the least. He has no idea how to answer the question he was asked, much less what's being discussed here now.

Can you substantiate your claim or not?
Wouldn't that make any language with reflection Duck-typed? That would suggest Wikipedia's definition is not very useful.
>We discovered that if we continued to challenge the accusation of infringement and lost, our video would be subject to copyright strikes. If the account was subject to multiple strikes its ability to live stream could be restricted or the account could be terminated. While our colleagues in the communications department were highly supportive of our efforts, they were concerned that one misstep could wipe NYU Law’s entire YouTube presence off the internet.

To be clear, if you dispute and counternotice everything, then the only way this would happen is if the other side actually sues you, which is incredibly unlikely here.
"Any branching model you choose is ultimately meant to make humans work together more easily to produce software"

There are things in this article I agree with, and things that I don't, but the quoted point is something that I wish could be universally understood. Some developers commit to the dogma of one blog post or another and forget about the fact that the whole thing is for the _people_ who are writing the code. Branching strategy should help to optimize workflows and minimize friction, regardless of how badly bastardized your approach is vs. its source material.
It's a commonly broken law in a lot of places.

Source: lived and worked in Australia, Canada, and the US.
Less than with a human driver, who can't see anything immediately in front and partially to the sides of the cab as well.
What? Shouldn't you try to make the creation and deletion of your staging cluster cheap instead of moving it to somewhere else?

And if that is your central infrastructure, shouldn't it be worth the money?

I do get the issue with having cheap and beefy hardware somewhere else, i do that as well, but only for private. My hourly salary spending or wasting time on stuff like that costs the company more than just paying for an additional cluster with the same settings but perhaps with much less Nodes.

If more than one person is using it, the multiplication effects for suddenly unproductive people, is much higher. Also that decreases the per head cost.
Hi Seth,

What about clusters that are used for lumpy work loads? Like data science pipelines? For example, our org has a few dozen clusters being used like that.

Each pipeline gets its own cluster instance as a way to enforce rough and ready isolation. Most of the times the clusters sit unused. To keep them alive we keep a small, cheap, preemptive node alive on the idle cluster. When a new batch of data comes in, we fire up kube jobs which then triggers GKE autoscaling that processes the workload.

This pricing change means we're looking at thousands of dollar more in billing per month. Without any tangible improvement in service. (The keepalive node hack only costs $5 a month per cluster.) We could consolidate the segmented cluster instances into a single cluster with separate namespaces, but that would also cost thousands in valuable developer time.

I don't know how common our use pattern is, but I think we would be a lot better served by a discounted management fee when the cluster is just being kept alive and not actually using any resources. At $0.01, maybe even $0.02, per hour we could justify it. But paying $0.10 to keep empty clusters alive is just egregious.
An Introduction to Time Series Forecasting with Python
This reminds me of large code reviews which have a million different things going on. After a while, people tune out and don't see bigger issues and quality of their feedback goes down, or they give up and say "yeah, all this seems fine to me". Compare that with a smaller code review with fewer things going on and where people end up being super opinionated on minor things.

The sort of lesson in this example is if you want to get some design decision through that you know may be controversial, bury it in with a bunch of other changes.

(Also related, the idea of announcing negative things on busy news days, i.e. "a good day to bury bad news".)
I am not sure I understand why this is a win for Uber drivers(genuine question). Is it considered a win because now they are treated as employees, so they will have benefits like sick pay, vacation days etc? What was the policy when they were not employees? Would they be penalized(financially) if they took a sick day? France already mandates some of these for contractors, so not a huge benefit, I think.

I doubt it'll mean more earnings, since employees are generally paid lower than contractors. This being in France, universal health care already covers everyone, so don't think that drivers are going to get a better healthcare coverage.

Maybe now the drivers will have to be compensated for wear and tear of their vehicle, which I can see is a win.
15-20% show severe symptoms, not just "symptoms". 80%+ show mild symptoms or are asymptomatic.
> For instance, judges in court have been shown to make poorer-quality decisions late in the day than they do early in the day.

This references the study "Extraneous factors in judicial decisions": https://www.pnas.org/content/108/17/6889

Here's an article, which has been posted on HN a few times, about why the conclusions of that study don't make sense: https://nautil.us/blog/impossibly-hungry-judges

Here's a concise HN comment about how the observed effect is explained without decision fatigue: https://news.ycombinator.com/item?id=14703990
Which Internet registries offer the best protection for domain owners?
I found this from 2017 https://www.eff.org/files/2017/08/02/domain_registry_whitepaper.pdf but I'm asking what you think in 2020, specifically in terms of censorship.
Currently I have a small cluster with 3 nodes running, each in a different zone (data centres next to each other, eg in London). Sadly this will now be charged.
One more shameless plug for my startup, https://kubesail.com (YCS19)!
What I've read about Coronaviruses is that most transmission is either through hand to face contact or droplet-suspended virions so a mask that doesn't protect against aerosolized droplets would still be fairly effective. I understand that surgical masks aren't intended to prevent inhalation of droplets but the substantial symmetry between air passing through one way or the other would suggest at least broadly similar effects either way. Given the empirical results from elsewhere in the thread it seems like that may be the case.
How can I deploy ML models as REST APIs?
I'm new to data science and investigating the best way to go from Jupyter notebook to REST API which I can send data to for ingestion into my data model. How are people doing this? I understand what's happening in my model itself, but setting up an HTTP server to send and receive data from my model is eluding me.
use of course, but they're still stocking up. Despite that I don't believe it's an issue. It's just prioritising supply.
There's a difference between something you personally experience and a general trait of all humans.
Editing tweets is against the core concept of Twitter.
So what makes anyone think this is the last?
jesus christ this is really what you took away from that?
NASA images: China's air pollution decreased amid coronavirus measures
Emerging Infectious Diseases Vols. 1 to 26; 1995 to 2020
Also, we will definitely commit to what I said we believe as company in our terms of service. As I have said we are in process to update them with more clarity.
Atomwise (YC W15) Is Hiring Senior Software Engineers/Cloud
Surprise: ”small random package” caused an issue in a Node project, and ”replacing [it] with simple init logic” solved the problem.
In your shed example, a builder could contact you and negotiate the price (perhaps the $100 price you set is completely unrealistic). That's not possible with Uber - there is no price negotiation - only declining/accepting a ride.

Similar argument for changing toppings on a cake - a caterer can negotiate changes to the cake - an Uber driver has no such flexibility.

Regardless, given corporate (human?) nature is to leverage any power differential to self-benefit, it seems reasonable that regulations be interpreted in the most protective (of the party with less power) manner possible.
Anti Airborne Respiratory Mask
$3600/year is significant for a startup on a shoestring budget.
There are different sources for different types of sensors. For example if the need is different types of gas/air detection I'd look at SenseAir as a vendor of affordable but still high quality.

The key thing I learned doing sensor projects is you need to define the requirements, operational environment, acceptable failure rate, range and things like the cost of downtime, criticality and accuracy etc. With sensor based projects it is even more critical to define the requirement simply because you can find cheap crap from China and it will sorta work under ideal conditions but may fail quickly when put into a factory or warehouse. So if you are running a business off them I'd rather pay the 10x cost for a quality sensor and not be replacing it every week and know that when shit goes down it will work, especially if safety is a concern.

For playing around, element14 (newark) and adafruit have all kinds of neat sensors to play with, then I usually turn to mouser or digikey or direct from manufacturer if you need quantity. Companies like GE, Siemens, SenseAir and a huge list of others make all kinds of sensors depending on the need.

Just thinking, predictive maintenance, might mean load sensors, wear indicators, level indicators, vibration, alignment (laser) etc, so I'd start with a few ideas of what you need and then ask as it might get you better recommendations (also search element14, adafruit for ideas). Especially if you can put some tolerances to the needs as tolerances will narrow down the right vendors much quicker.
I'm one of the authors of this paper, along with Fan and Tao. I'm also a huge fan and religious reader of The Morning Paper, so it's really cool to see Adrian feature our work. If you don't know The Morning Paper, be sure to check out some of the other stuff that Adrian writes: deep looks at a mix of systems, ML, and even classic papers.
Reminiscent of the Polio outbreak/iron lung era. A survivor described the sound of clicking tounges in iron lung rooms after the electricity had failed and a few nurses needed to rotate between devices, manually pumping air. Tounge clicking because no one had the ability to exhale air and produce vocal sounds.
The difference is that it's impractical for Uber drivers to directly solicit customers, because too few ride at predictable times and places.

Handymen, cleaners, developers, hairdressers etc can (and do) establish relationships outside the "advertising platform" and can find a meaningful number of new clients (and total $) through word of mouth.
Please go to investing or personal finance, you're worse then OP.
> Parents – children playing anywhere make noise. When they get quiet, you get to them and find out why.
Who cares for software engineers in bandanas anyways if you can have bank clerks in bandanas!

And even that would hardly look weirder than in surgical masks. Color-coordinated bandanas with a company logo pin?
The "solution" they arrived at boggles my mind:

> We reached out to YouTube through private channels to try to get clarity around the copyright strike rules. While we never got that clarity, some weeks later we were informed that the claims against our video had been removed.

We need competition in this space.
There was plenty of ruthless capitalism before he showed up. He just pushed it to be more ruthless.
Quick review:

Very neat presentation. I often work out this sort of thing in my head or on paper.

I was confused by the wording initially. "Enter a list of what you want to decide" sounded to me like I should enter separate decisions ("What should I eat for lunch?", "When should I mow the lawn?", …). Perhaps word it as "Enter the alternatives you are trying to decide between".
The (press release of the) judgement does not address a key counter argument: a large majority of drivers work for several platforms simultaneously. Even if that particular driver did not, he obviously had that possibility: the switching cost are negligible for a driver.

Source/disclaimer: used to work for a direct Uber competitor in France.
I think I developed that from too many stand-ups. :v
The main differnce is that the handymem can easily look for other customers elsewhere to find an alternative job. Uber drivers don't have this choice. They can't do a counter-offer neither.
Technically, as you said, they can refuse. In practice, the power that Uber has on his drivers limits those choices a lot.
> Many people would need additional tooling to parse JSON into a structured type, especially in dynamic languages where unstructured data types are the norm.

Well, there's your first issue. Specifying your formats is a good idea, regardless of language. And this is completely possible in dynamic languages too, see for example Python's Marshmallow.[0]

> And even if you do that, you're still going to have to validate the data and tell the client where they might have messed up the formatting.

The point is that you should take the opportunity to encode this validation in your types. A validated email address is no longer a `String`, it's an `Email`, with different valid operations. Or for an extreme example, you (hopefully) wouldn't try do time calculations directly on RFC 3339 strings.

This doesn't have to happen at exactly the same time as parsing the JSON AST, it's completely sensible to go JSON -> JSON AST -> Model.

[0]: https://marshmallow.readthedocs.io/en/stable/
I use an external USB drive. You can get anywhere from the standard thumb drives, up to multi-terabyte larger drives. So when travelling I just take whichever drive I need and whichever laptop I need, and plug them together.

It isn't exactly syncing, but it solves the problem, at least for me.
Nope - I don't any any of those needs (few in general actually). It's more that this possible decision point is gone. It's uplifting, at least for me.
Only when using the native screen shot app, which you can use many on Android.
You're probably thinking of "blood quantum." It's... complicated.

https://www.npr.org/sections/codeswitch/2018/02/09/583987261...
My guess: Sharpening is the process of removing material, if you sharpen a knife forever it will grind down to a useless stub. It is possible something got lost in translation, or possible that the metaphor isn't quite as satisfying as some of the others used.
I used a watered down version of gitflow on a project with heavy customer involvement.

Instead of doing the whole thing, we had feature branches (which I still hate), master, and one more branch for the stuff we were showing to the customer. Who sometimes would decide they didn't like what they asked for and please don't push this to production.

With the exception of hotfixes, master was always just a certain number of commits behind the working branch.

Very aggressive use of dark launching of features could also solve this problem, but we've had our share of problems with that strategy too (Sprint-obsessed thinking makes it difficult to go back and clear out old conditionals once they've settled)
That's not how I read that. "lost" in this context simply means the so-called copyright holder clicks the button that says "nah, still can't use my stuff" that's considered a strike.
> While our colleagues in the communications department were highly supportive of our efforts, they were concerned that one misstep could wipe NYU Law’s entire YouTube presence off the internet.

The copyright system on YouTube is broken and stuff like this allows rightsholders to abuse the DMCA and bully small creators. It's a shame.

> Since we are the center at NYU Law focused on technology and innovation, it was not a dead end for us. We reached out to YouTube through private channels to try to get clarity around the copyright strike rules. While we never got that clarity, some weeks later we were informed that the claims against our video had been removed.

It is so with all Google products. Your content will be taken down or account will be randomly locked or your apps will be removed and unless you have lots of "clout" and/or can build up an outrage about the incident on Twitter/HN, you're screwed.
With Google's questionable policies, buggy automatic decision-making and notoriously terrible support? Unless they're sure they can make their complaint go viral, the risk feels quite high.
Those empty clusters that you get for free cost Google money. Perhaps it never should have been free, because that skewed incentives towards models like this.
Taxi drivers can pick up anyone on their own terms (with some limitations from local laws). Uber drivers on the other hand can only legally pick up rides dispatched from Uber or another ride-sharing app. That's all they're insured for and that's all local laws will allow because they don't have status as licensed taxi drivers in a licensed vehicle.

A customer can hand me cash and nobody gets a piece except the government. An Uber driver cannot accept cash or payment outside the Uber app or they will be fired.
What exactly are these people doing all day? I can't point to a single notable product innovation they've had in years.

Maybe Twitter is less caught up on the SV "gotta change/break something user-facing today to justify my job" treadmill than other tech companies. Or maybe the changes they make are on the back end. It's been a long time since I've seen a fail whale.

Considering the global societal impact that Twitter has, I'm surprised it has only 5,000 employees.
You're just using expertise as synonym for authority.
I don't think they've ever had radios in though, doesn't seem likely that they also take dispatches.
Yes.

https://en.wikipedia.org/wiki/Buffalo_Billion
Well, you claimed that Lisp programmers can not work in software teams over a long period of time, because they don't understand each others code. I gave a few examples.

There are also a bunch of examples where Lisp was used to prototype or for rapid application development. This enables exploring ideas or conquering early markets. Later iterations may then reimplement the thing... That's another model and is also fine - though there are projects which had not much experience and were not able to get the thing off the ground. For example the first version of the Postgres database was written in a mix of some Lisp implementation and C. This did not work well for them and they switched early away from Lisp. Similar the first version of Reddit was written in Lisp, but it did not really work that well for them and they switched to Python.

> The implication often given is general purpose productivity superiority

I don't think that claim makes sense in general. Much of the productivity in modern software development does not come from the programming language. Much more important nowadays is the general eco-system.

For example it makes very little sense to develop apps for iOS in Clojure, since there is zero support for it from Apple. Thus most iOS applications are written in Objective-C and/or Swift. An assumed 'general productivity superiority' doesn't help at all to compensate the total lack of platform support from the platform provider.
I think a lots of people end up having a reaction like "well they're trying their best! what else are they going to do!? it's basically an impossible problem!" to things like this and other recent youtube headlines.

That reaction betrays an assumption that YouTube must exist at its current scale in its current form, just because... it does already. And I think that assumption is dead wrong: we're bumping up on all kinds of emergent phenomenon (conspiracies, runaway recommendations) and issues (copyright, borderline child porn) that cannot be solved, and we shouldn't let Google give us their best-effort compromise. If you can't address these kinds of problems in your product, don't fucking build it.