skysight-inc/HackerNews huggingface dataset:
While I spend a bit of time fixing other people's messes, I have to agree.

I find the biggest issues are people who don't really understand Git enough doing silly things, or just being careless. Like somebody cherry-picking something to Master and then cherry-picking it to a branch we're working on, but on top of some stuff that has changed in that branch, requiring them to fix a merge conflict. But then when it comes to rebasing the branch on Master to merge it, you then have two more conflicts to deal with that you didn't need to have, if it had just gone once to the right place! It's not hard to fix, but annoying, and you risk introducing errors to the code if you accidentally miss a line or something.

So the biggest issues are probably 1) people not following our workflow, creating extra work to fix, 2) people not understanding Git enough; or possibly for some people, 3) you team/company's git workflow isn't very good.

In most teams for 3 (which is probably one of the more common ones), you really only need one or two people who really understand Git well to set up the workflow and enforce it.
One of the challenges of git a decade ago was that people created branches everywhere and it became difficult to reason about what branches were doing and what work should be done in them.

Git flow, at that time was the most reasonable model for git branching.

By reasonable I mean "able to be reasoned about". If I see a feature branch, I know what should be in it. I know what should be in a release branch. I know what the state production is in.

It isn't the best branching model - but when faced with the contemporary other branching models, git flow let was an attempt to put some order to that.

It also works fairly well. It isn't so much that its dogma, but rather that it is consistent and understood across different teams. The problems that it solves in communication are more important in many places than the ones that it causes in other parts of the workflow. Coming up with a new workflow isn't hard - just that one now needs to solve a different set of problems and most people don't want to have to solve those problems... and so git flow is an acceptable default.
Maybe it was actually a self driving truck transporting a self driving car.
I moved on to molecules https://thischemicaldoesnotexist.com Perhaps short stranded proteins are next
They actually are a middleman (travel agent). I stick to dealing directly with the big hotel brands, as their policies dictate that if you aren’t able to be accommodated, then they will find you an equivalent room and pay for at least the first night. And if they can’t do that, I would trust them to compensate some other way.

Otherwise you can just do a chargeback and claim services not rendered and you should get your money back that way.
I wonder if an Uber could exist that posed itself as a service to drivers not passengers.
This person should look harder. I know plenty of people used to operating at exponential growth and the growing pains it implies. Plenty of financial and biological systems require it.

The realistic view is also that nothing stays at exponential growth forever. It usually tapers off until something changes. Yet people demand everything stays the same with growth year-on-year at same rate. Past performance does not imply future performance but useful patterns can be found if you pay attention.

Extrapolation requires experience. Easy way or hard way.
Then manage k8s yourself.

Or, better yet, don't use k8s. You don't need it, especially as a startup on a shoestring budget. You can migrate later if you decide you really need to, but just a plain LAMP gets you 99% of the way.
On Infantilization in Digital Environments (2015)
People don't ride around town on ICBMs every day.

https://www.youtube.com/watch?v=snTaSJk0n_Y

And planes still occasionally drop ICBMs that destroy people's houses.

https://www.independent.co.uk/news/world/americas/frozen-exc...

https://en.wikipedia.org/wiki/Blue_ice_(aviation)

Steve Wozniak likes to put stickers in airport bathrooms that say "DANGER: DO NOT FLUSH OVER CITIES".

https://twitter.com/stevewoz/status/912498392223252481

https://webfactory.mk/2018/05/28/do-not-flush-over-cities/
Do you remember the hellish experience that was SVN, or CVS?
if it's a shared car, you could pick up customers from multiple apps on the same trip?
Are surgical masks sealed around the edges? I've only worn N95 before and if you don't have a proper seal you're not even filtering the air. That's what I've always assumed was the problem with surgical masks. It's not that they're not a good enough filter, it's that they aren't even filtering the air when you breath in. But I might be wrong.
> The new proof establishes that quantum computers that calculate with entangled quantum bits or qubits, rather than classical 1s and 0s, can theoretically be used to verify answers to an incredibly vast set of problems.

LOL this was the original promise of Quantum Computers. I would think a proof would be a quantum computer that actually delivers on that promise.
Null is not the problem there, null is the symptom. You see exactly the same problem if the val is a primitive type (which can't ever be null): if you access an Int from a mixed-in trait in an earlier constructor, that Int will be 0. This is a real issue, and one where I think Java has actually made the better design choice (interfaces may contain method implementations and constants but not fields - of course they had the benefit of Scala's experience when making that decision), but it's not about null.
My reaction to '10 years' also. I recall using some (forgotten, Mac) inpulse conv in the early 2000s. (Not real-time!) This SOS article links many reviews dating back to 2002-04 (the earliest for the Audio Ease 'Altiverb'). https://web.archive.org/web/20161209164745/http://www.soundo...
Regarding your button question:

You do need some sort of seam at the point of use so that the feature flag logic can be hidden behind a lookup function. For example in Rails you might include your button code via a partial template. You could use a view helper to provide the name of the partial and that helper could respond with different names depending on the feature flag:

<%= render partial: primary_button %>

def primary_button
feature_flag_enabled ? "new_button" : "button"
end

Obviously the particulars are going to be different in different frameworks.
TCP coming into your cluster means that you practically have to go through kube-proxy (because the load balancer and the Kubernetes scheduler aren't perfectly synchronized) and that the load-balancer can't balance per-request, only per-connection. If the load balancer terminates TLS, then it can just watch cluster endpoints and automatically route to the right node without any extra hop through kube-proxy, and it can also split large individual requests out of HTTP/2 and GRPC streams.

I'm guessing 99% of workloads won't notice either of these issues, but it is an actual issue.
My mind was blown when I found out that daily standups were a Kanban philosophy and not a SCRUM philosophy. Only because every SCRUM team I have been on has standups and it is essential, as long as they are less than 1 minute long.
“what Waymo is doing to help support the existing drivers, ”

Waymo should be doing nothing. Companies should work on improving technology. The problem is to distribute the gains. That’s what social safety nets are for. And progressive taxation should help to distribute gains from technological progress widely instead instead of only to a few capitalists. I am aware that this may be an unpopular opinion.
Why would he "complain"? or say anything on that mailing list? More than that, it's still git version 1 right? Sigh.
> Pretty sure the fatality rate is based on the number of patients who present themselves to a doctor.

I don’t think this is right. I believe it’s based on an estimate. Your own numbers bear me out. The flu death rate is estimated to be around 0.1% and we can come to that number by a division here:

“ The overall burden of influenza for the 2017-2018 season was an estimated 45 million influenza illnesses, 21 million influenza-associated medical visits, 810,000 influenza-related hospitalizations, and 61,000 influenza-associated deaths”

So 61/45000 = .14%
do you bring your own servers too?
It seems... strange to call Workspaces Application Manager “a VM you tried to spin up”

Workspaces are already a specialized product built on the AWS ecosystem; WAM is a niche management tool inside that niche.
Suppose that Alice and Bob share a seed to a RNG before the game starts.

Can you explain how this will allow them to always win the game?
Update 8:30 eastern..

Outside of China : 273/1259

Inside China: 3,012/52,045
brisbane has 80-90% humidity and temps around 30 a lot of the time. what would persisting moist hot air do, to your rainfade?
to have any employees show up to work
Load balancers are created by the pre-installed controller that each cloud provides to let external traffic reach the nodes. You don't have to use it.

It's no different than running your own load balancer like HAProxy pointed at the nodes which forward to a node-port service.

There's also MetalLB if you're running your own hardware: https://metallb.universe.tf/
Always helpful to think about your future self as that other person.
I'm not sure what you mean by "proposing what continuity holds for the quantum system".

There are a number of results about how measurements of an individual infinite-dimensional quantum system can be approximated to arbitrary degree by an arbitrarily large finite-dimensional system.

This new result seems to suggest that for joint entangled systems there's a "buffer" between measurement results obtained by having arbitrarily many dimensions, and by having infinite dimensions.

I was wondering how practical it could be to actually do an experiment and verify that the buffer line is crossed.
> The WHO has collected stats from tens of thousands of cases...

This part is inaccurate. The WHO's best quality data set is South Korea, which is only a few thousand cases (the vast majority of which are still in the early stages of the illness). The data quality in places like Iran, China, and even the USA are TERRIBLE and should not be used to draw any conclusions.

Additionally, the R0 is clearly different in different climates, so places like Singapore, Thailand, Vietnam, Malaysia, should not be used to infer infectivity in colder climates like Korea, Taiwan, Japan, Europe, and America.

A great source for facts is the TWIV podcast - twiv.tv. They are experts in Virology and infectious disease control.

> most people get fevers

This is a bit misleading when the WHO says 3.4% of people die, and 5-10% require intensive case and mechanical ventilation. According to the CDC, the flu kills 0.05% of the 32 million people infected in the US annually. A 100X increase is devastating for healthcare systems. The systemic problems occur when masses of older people require more ICU beds and ventilators than are available, which then drives the mortality even higher.

We should be tremendously thankful that children do not seem to be impacted. If it weren't so, the level of panic and economic damage would be significantly higher. Schools would already be closed and a HUGE portion of the workforce would be unable to work.

> ...stopping the spread is completely impossible, while we have seen by example that it isn't.

Given the global spread and the lack of testing in most non-first-world countries, most experts agree that the disease will not be contained and will become endemic. Think about North Korea, Mongolia, or Nepal - the fact that they are not reporting cases, should not be interpreted as evidence that no cases exist.

The recommended WHO strategy is to SLOW the spread of the virus with a balanced strategy of containment and mitigation. The goal is to buy us enough time to develop and deploy a vaccine.
I don't understand why this is so complicated. If someone works for you, they are an employee. If someone works with you, they are a contractor. I think the French definition of subordination is a great defining characteristic. However, my understanding is that US law doesn't make this distinction thus introducing a gray area.
"kubectl explain deployment"
The first one sells for $20k. The second one doesn't sell at all.
But if you are robbing an autonomous vehicle, you're probably going to be recorded doing it, and fleeing, which raises your risk because it leaves a pretty strong evidence trail. Yes, ski masks can be used to obscure your face, but car makes can be tracked if the getaway car has no plates.

If this becomes a frequent enough issue to matter economically, then perhaps we should start looking into what incentivizes stuff like that in the first place, and deal with it.
Yes. So often I've seen art that is completely devoid of meaning without the label, and it isn't obvious if the label is supposed to apply to a nearby pedestal or the wall it is affixed to. The label is the actual art work.
Show HN: How to make your office more intelligent
to me seems a very simple first step:
just require extention devs to notify people on owner change, possibly with a standard way...
just a lil popup or icon asking "extention X has been aquired by Y, it has permissions A, B, C, D, are you OK with this?"
> Sometimes it's called `powershell` and sometimes `pwsh`

This probably isn't something kbd would run into; the command is always `pwsh` on macOS/Linux.

Windows users get `powershell` (Powershell 5) and `pwsh` (Powershell Core 6 and Powershell 7) for backwards compatibility reasons. It's another `python` vs `python3` situation.
It's come up here several times, for example: https://news.ycombinator.com/item?id=20050173
From my days working at a perforce shop... Advanced SCM Branching Strategies was something that I was familiar with. https://www.vance.com/steve/perforce/Branching_Strategies.ht... (from '98).

The essence of it is establishing different roles for different branches. mainline, development, maintenance, accumulation and packaging.

With those roles in mind, when I was introduced to git flow it made sense - mainline is develop branch; development and maintenance roles are done in feature branches. Accumulation isn't one that is seen too often but should be kept in mind, and the release branch is the packaging role.

These ideas have probably been realized time and time again.

The conclusion of the paper:

> Planning and analysis are critical to the success of any SCM system. A branching strategy motivated by a risk-based analysis of the organization's development needs will provide a strong foundation. Incorporating the concepts of branch roles, codeline policy and codeline ownership will assist in performing the required analysis. Application of the principles of branchpoint, merge policy and branch life span will ensure that the parameters governing codeline policy are properly and completely addressed.

> Once the branching strategy has been formulated, the organization can implement the customizations required to make the SCM tool suit its environment. Until SCM systems have reached sufficient maturity to address the larger issues of policy, adopting the practices put forth in this and other papers will help an organization achieve success in their software development endeavors.
> If you've never had a git commit FAIL...you aren't very experienced with git. By your description, you've probably just used it casually a lot. You don't do anything complicated and conclude that git isn't complicated.

You make unwarranted assumptions about another person's experience base simply because it supports your position to do so.
How I Transitioned from Ease to Spring Animations
> Huge segments of the economy would fall apart of we made all of those kinds of people employees.

I don't think that's really a relevant argument to whether they should be classified as employees. Huge segments of the economy have already fallen apart, and more will fall apart in the future.
> It's basically what you describe. The compiler generates generic code that can call into a variety of "codecs" but they don't have to actually be serialisation specific. So there are codecs for JSON, protobufs, CBOR etc but you can also do arbitrary object graph transformations with the framework. A deep clone being a simple hello-world type example.

So what does the value that gets passed into your codec look like? What makes Shapeless tick is that it can represent records generically at the type level; records will have a type like

type Book = 'author ->> String :: 'title ->> String :: HNil

that you can actually break down and do meaningful operations on (e.g. you could run it through a function that counts the lengths of strings and get something of type 'author ->> Int :: 'title ->> Int :: HNil, in a fully type-safe way). I'd be impressed if someone managed to encode those kinds of types into Kotlin - e.g. I don't think Kotlin has singleton types, so being able to compare field names at the type level is probably impossible?
I’d encourage anyone using Git take a closer look into “git rebase -i” (interactive rebasing) combined with “git add -i” (interactive staging).

While working, I’m freely taking advantage of Git’s capabilities on a personal level, producing many sometimes messy WIP (work in progress) commits, trying things on short lived branches, reverting changes, and so forth, but afterwards I am able to copy edit the results to produce a sequence of finalized commits that form a coherent narrative that reads like how I would describe my work to a colleague or manager.

To me, interactive rebasing has been the difference between “my team uses Git” and “I first and foremost use Git for myself, and then also use it to share the results with my team”.
Gravity 7.0: Run cloud apps in restricted, regulated, or remote environments
> because they include aspects which resemble computers

Other way around, these computers we use resemble us (however not particularly closely) because we created them, not vice-versa.
The article mentions a mismatch of 4KB (Linux) vs 16KB (iOS) page sizes. Further reading:

https://github.com/torvalds/linux/blob/master/Documentation/...

https://developer.apple.com/library/archive/documentation/Pe...
Well, enough people seem to believe it that I had trouble buying hand soap a couple days ago.

It had not even occurred to me that people might be buying up hand soap due to coronavirus. After all, we are advised every year to wash our hands frequently to reduce our cold and flu risk, and to wash our hands after using the restroom. Thus, I expected that most people already regularly buy hand soap, and so being told it is also good with coronavirus would not lead to a noticeable increase in demand.

Apparently, I greatly overestimated the basic hygiene practices of my fellow citizens.
I just discovered the news / comedy podcast No Agenda. [1] Hosted by Adam Curry and John Dvorak. Apparently this has been a thing now for ten years!? Sort of a hidden treasure. Adam was on Joe Rogan recently to talk about how he invented the Podcast format years ago. [2] It seemed to capture a lot of Adams enthusiasm for researching and explaining what makes the world tick.

I find that No Agenda consistently delivers insight and entertains, with a producer driven podcast twice a week. I am grateful I found them as my commute is much more entertaining! While they fund this based on donations, they accept no Advertising so it has a very refreshing feel to it.

[1]: http://www.noagendashow.com/
[2]: https://www.youtube.com/watch?v=NaPKrZTUoUs
More money goes to government.

Less (or in the best case the same amount of) money will stay in Uber driver pockets because of the taxes

Less money in people's wallets because of the higher transportation costs.

Who have more money have more power :/ This is how we loose freedom
As a driver, every once in awhile I glance at the faces of other drivers on the road.

Sometimes I get the feeling that more than 50% of road-time in the US is spent looking at a phone.

It's enough to make me wonder if "x% of accidents involved texting and driving" is even a convincing metric. If god damned everybody is texting and driving all the god damned time, of course lots of accidents involve texting and driving.
Throwaway username suggests that MS also directed employees not to publicize this.
This process reminds me of "Considered Harmful Considered Harmful": https://meyerweb.com/eric/comment/chech.html
I used to work at a gig economy startup (uber for dog walking...) and we spent considerable resources lobbying local and national governments to expand the kinds of restrictions we put onto our independent contractors while still not labeling them as employees.

We also had an entire team dedicated to preventing our contractors from going "off platform".

Probably one of the more exploitative jobs I've had.
The person clicking the button just needs to think it's true.
It's not the smoothest, but at least it's fairly stable/consistent with good performance (vs. e.g. an electron GUI app). Once you get things dialed, you can keep your workflow going for years with minimal changes since nobody is trying to make money trying to sell you a new version of your workflow. I do a lot of work over SSH, too, so it's really nice to have my regular workflows largely port over to remote work.
> Anybody who still says it's all fake is just jacking off on nationalism.

I mean, they're hoarding toilet paper for a reason...
EKS feels like a product where Jeff Bezos walked into a room and said "you're all fired if you don't have a Kubersomethings service up in the next two weeks". The team did it and haven't touched it since.

The amount of management they make you do is amazing. Need to upgrade the kernel on your nodes? Fill out a five page CloudFormation workflow, and if you copy-pasted anything wrong, your cluster will just randomly work strangely for no reason. This is what they consider "fully managed"! (There are also lots of neat bugs, like if you create a cluster in the web interface while logged in with SSO, all credentials necessary to access the cluster will disappear in an hour. By design, apparently. So even though they have a web interface, you have to create a role account and use the command-line.)

It's really a wondrous product and shows how complacent you can be when you're in first place.
There's a ton of infrastructure to build and maintain at Twitter. Yesterday's solutions don't scale and need replacing. Yesterday's "just get it done, we'll worry about cost (or quality, or operational burden) later" have happened and it's time to fix. Lather, rinse, repeat.

This post should give you an idea of scale at Twitter. When I worked there, I spent about 2 months focused just on creating software to help automate the Clos migration mentioned. And there are just tons of things like this that are constantly being worked on.

https://blog.twitter.com/engineering/en_us/topics/infrastruc...