skysight-inc/HackerNews huggingface dataset:
> I dont even get why people rebase for a merge. I never did this and I get the entire history not a distorted version of it.

Except that the history is disorganized and is not organized into distinct patches that only do one thing where each patch has a well written commit message.

People seem to want to treat the VCS as a back up system rather than a system to keep track of changes. Technically you could get the former by configuring your editor/IDE to generate a commit every time you save the file, but that in itself would lead to a very large history that wouldn't be useful (meaning commands like git blame would be next to useless).
Both AWS and Google offer free tier products and pay-for-what-you-use products. Reserved instance pricing starts at around $25/year. Many other incredibly useful products (S3, Lambda, VPC, etc.) are free with an instance or start at $0.

You can set billing alerts that will project your monthly budget every hour, and send you an alert when it's projected to be exceeded.

IMHO your claim (that there is an entry cost barrier) is the opposite of reality. AWS and Google have brought incredible power and choice to developers starting at zero initial cost.
You sir have a very warped view of SV. Do not stereotype us.
Sometimes it’s just that by taking enough out, it becomes unclear and complicated. I “taught” eXtreme Programming to two of my own teams by showing them the book. Worked like a charm. I also participated in several “Agile” installs that failed despite training, meetings, demonstrations, etc. All because removing the “customer is in charge and developer is allowed to get the job done as they see fit” component made it complicated.
> When people dislike a source they will often dismiss the entirety of the content.

Pandering to these people on Hacker News is counterproductive.
I don't know what the CGT situation is in America, but in Australia of you own an asset (shares, property, etc) for less than 12 months before sale, capital gains tax kicks up to about 50%.
Proven ways to craft a top-notch UX
In Seattle, the best current estimate (https://bedford.io/blog/ncov-cryptic-transmission/) is 570 infections as of March 2:

> Knowing that transmission was initiated on Jan 15 allows us to estimate the total number of infections that exist in this cluster today. Our preliminary analysis puts this at 570 with an 90% uncertainty interval of between 80 and 1500 infections.
On the contrary my team and I have been having great luck with git-flow.

When I onboard a new team member I watch them struggle with git-flow and for me that's a great thing to see because I see them learning an efficient way to work.

Once they 'get it' everything flows smoothly, and everyone has the same way of working which makes it very easy to see and help debug when things happen. Communication is also consistent across all team members partly because of the git-flow branching model. We as a team understand why / when to use feature branch, when to use hotfix, when to cut a release etc... That's what I expect from a team. Git flow has been great for our team and workflow.

To each their own. I guess I will continue recommending git-flow.
Gofmt will add and remove spaces to imply order of operations.
If I’m running a startup trying to develop a product with limited staff, the last thing I want to be worried about is the “undifferentiated heavy lifting”. I want to be concentrating on what is going to add business value.

Then again, I know enough about AWS and how to control my cost.
I’ll assume that they’re VPN’ing into work and their IT doesn’t allow split tunneling. As a result, all traffic has to flow into the VPN concentrator as a bottleneck.
> I hate rebases because they create multiple hashes for the same logical commit

Some of those commits may have changed (either the commit message or the diff itself). There's a git command called range-diff[1] that was added recently that allows you to diff between rebases.

> Also, they tend to involve more manual processing, and thus human error, then merges.

Before actually pushing up the rebased branch, you run a diff against the upstream tracking branch to see if any inadvertent changes were introduced. For example:

git diff @{u}..

And use the range-diff command to see the difference between the upstream tracking branch and your locally rebased branch.

[1] https://git-scm.com/docs/git-range-diff
CRDs can’t be safely namespaced atm, aiui.
One of the benefits of globalization (and the EU) is that it's to everyone's economic advantage to not have a war between trading nations. This maintains supply, reduces costs, and crazily enough - reduces conflict.

You may lose the ability to make widgets because it's easier/cheaper to buy them from another country, but in theory, you make it up by selling them sprockets, and through the overall economic gains.
You need to consider what you are going to spend that money on.

Seriously, unless you think that your share is worth a vast amount more like 25-30X more..., take the buy out.

You are talking about what maybe the minimum amount needed as a retainer to procure a lawyer, so take the money, move on, it was a great investment that was profitable.

You said it was 5 years ago so what are you hanging on to?

If you have a good relationship with this company, or the person making the offer... take your ransom and stop holding your 1.5% hostage.

But who am I other than a random person giving you free advice..you get what you pay for right?

Still take the money, chances are it is less than it's worth but what it's worth and what you will get are not necessarily the same amount.

Take tge money!!!
Not in Florida, https://www.alperlaw.com/florida-asset-protection/
"54 of those 445 people developed new or worsening symptoms"

So we're basically having people make themselves sick by watching the news, its a brand new pandemic!
Ah interesting, didn't know about that. Seems like a easily exploitable loophole if so.
Primary residence in Florida is shielded from bankruptcy and creditors. Also retirement accounts (both IRAs and 401ks). Lease your expensive ride and you’re mostly judgement proof.
boy this comes across really tone deaf. GCP makes it very hard to change e.g. multi-region settings, but I guess it’s the customer’s fault for not already using this contextless name-dropped best practice.
As someone who lives in NZ and works in the US market, I cannot wait for this to end. As every year I have 4 time switches.
You know there is a favorite function already right?
> I watch them struggle with git-flow and for me that's a great thing to see because I see them learning an efficient way to work

Maybe they're struggling because it's not efficient, or intuitive?
> large number of young people too

Most of the info I've seen on this suggest that the young aren't particularly susceptible to the virus.

https://www.cdc.gov/coronavirus/2019-ncov/specific-groups/ch...
How could he possibly think he could get away with stealing files? Stealing "IP" seems a little less concrete.
> I've had to spend time fixing history after a Jr engineer did a bad rebase.

I tell people to run git log -p --reverse origin/master.. on the rebased branch and check that everything works before they push up their branch to the remote. I also tell them to run git rebase --exec "linting-command" --exec "unit-test-command" --exec "integration-test-command" and make sure that tests pass for every single commit. If they don't, then they spend time fixing it until they do.
> This sounds like pure speculation and is probably not a reasonable thing to assume.

It is speculation, but not pure speculation - there is some data to back it up.

Trevor Bedford [0] is a researcher at Fred Hutch in Seattle and a professor at UW, focusing on genomic sequencing of viruses.

He estimated two days ago [1] that the number of cases was in the hundreds, with a large degree of uncertainty:

> This approach leads to a similar estimate of the number of current infections at 330 with a 90% uncertainty interval of between 20 and 1500 infections.

This is solely an estimate of the infections here in the Seattle area, based on gene sequencing.

0: https://bedford.io/team/trevor-bedford/

1: https://twitter.com/trvrb/status/1234589820946534401
It’s is, but the benefits outweigh the moral hazard.
Stitch Fix: Introducing Our Cultivating Algorithms Visualization
Why does Alexa / Google Nest harm wireless networks?
I work for a WISP and do lots of housecalls where the internet has gotten slow.

I've learned a strange lesson through repeated experiences: After checking all other known variables, the question must be asked:

"Ok, do you have an Alexa?" (or Google nest).

A surprising amount of the time the answer is "Oh yes!" and by unplugging it, we find it's as though we had performed a technological exorcism. All the bandwidth demons are gone.

It's not only a bandwidth thing. Google Nest and Alexa completely crowd out other devices, and do something to the router where you can't even get an IP without powercycling it. I don't mean to be vulgar, but Nest and Alexa seem to gang rape everything on the network.

I haven't taken it as far as bringing one home and watching it's activity, to spy on the spy. One thing I can confirm, though, is that the bandwidth issues do not always come from Alexa / Google using the internet.

I've seen a lot of WISPY people on hackernews, so I thought I'd throw this question out there.
If people were taking home $100k driving for Uber I would accept this argument, since I wouldn't want to interrupt the good opportunity with regulations.

As it is, I see the preponderance of arguments on the side of it being regular employment without the expected benefits.

For what it's worth every Uber ride I've taken I would have taken at double the price, it's possible they could afford to pay their full time drivers benefits.
While that is technically true, in practice the private entities are beholden to the creators themselves, and the viewers stand up for those creators.

If creators and viewers knew definitively what was legal and what was not, they would choose to fight back loudly and publicly. My proof? Despite that solid footing, they already do.
IMO part of this is that at every step there are a number of scenarios that could occur (from "bad flu" to "1918 all over again"). As we get more information and see this unfold, we can update our scenarios based on new information. However, I haven't seen too much reporting that lays it out in this way.

This leads to some people drawing conclusions like "wow I was lied to, they said it wasn't bad and would be contained to China," which isn't entirely true.
Agreed. However, "improper secret management" does not accurately describe Levandowski's actions, and one could argue that he did abuse his power at the expense of others.
For those interested, the arxiv link: https://arxiv.org/abs/2001.04383

Be warned, this is 160 pages of dense math. To anyone complaining that the quanta article is "unclear" or not descriptive enough, there's no way around that when summarizing a dissertation.
Why was population density low? Perhaps even a small clan would need a wide territory to hunt/gather what they possibly could. Neandertals may very well have had greater caloric needs than early homo-sapiens.

Territorial conflicts could be quite common if a tribe required a large area, more chance of it coinciding with another's territory.

One could speculate maybe that could be what the cro-magnon special sauce was. The ability to survive off of smaller territories - or feed a greater population off of the same.
Plenty of footnotes if you want to dig into the details / weeds:

> Conclusion

> In summary, the scientific literature strongly argues against the switching between DST and Standard Time and even more so against adopting DST permanently. The latter would exaggerate all the effects described above beyond the simple extension of DST from approximately 8 months/year to 12 months/year (depending on country) since body clocks are generally even later during winter than during the long photoperiods of summer (with DST) (Kantermann et al., 2007; Hadlow et al., 2014, 2018; Hashizaki et al., 2018). Perennial DST increases SJL prevalence even more, as described above.

[…]

> Summary

> Discrepancies and misalignments between social (local) clock time, sun clock time, and body clock time can be caused by political decisions: DST is one example. There are multiple health and safety consequences of these misalignments. Our goal is that this article’s facts and reasoning will be used to make clock choices that improve human lives.

* https://www.frontiersin.org/articles/10.3389/fphys.2019.0094...
The golden age of neutron-star physics has arrived
>That's why everyone should still use SVN

Ah yes, good old normative claims.

The market wants what the market wants.
The approach that has worked best for me is pretty simple.

Master should always be in a deployable state.

Any commit that lands on master must include unit tests that demonstrate that it works (or at least doesn't break anything).

Incomplete features that will take more than a week or so to develop should be merged to master early protected by feature flags. This avoids long running branches.

I like squash commits: build a feature iteratively in a branch + pull requests, squash to master once it has the tests and documentation bundled together with the implementation. This gives you linear history.

People who prefer to review smaller commits can do so in the pull request - it's only the finished item that gets squashed into a larger commit.
So don’t make that kind of mistake going forward.
One way, is to start something up, and then get acquired by Amazon, Netflix, or any other larger player that has the infrastructure for it.
I liked CVS with continuous integration. It was problematic if you strayed from the trunk for too long. But one of the big reasons for SVN was to handle directories and version them properly.
“Rebase” is a bad name for what should be called “edit history”. Never edit the existing history of master. Always do edit the history of other branches to merge them into master.
This looks like a good starting point
https://en.wikipedia.org/wiki/Interbreeding_between_archaic_...

And

https://en.wikipedia.org/wiki/Human_evolution#Neanderthal_an...

Neanderthals are thought to have split from Sapiens between 180K and 800K years ago.

It looks like the science is not settled on whether Denisovan separated from the common ancestors of Neanderthal and Sapiens or whether Denisovan are closer to Neanderthal.
What do you mean a weak aggregator? eBay sellers have ratings, have their ads ranked and surfaced based on rating and other algorithmic criteria determined by eBay, and sellers must comply with instructions given by eBay w.r.t. listing, selling parameters, payment, contact, delivery, diverting sales off platform, etc., or be deranked, delisted, or kicked off the platform for non-compliance. Literally the same thing, except with goods + services instead of services alone.

Yet sellers are not employees. Your hue and cry that it is different does not compute.

In fact, you see this degree of control or more over participants in every market, forum, or platform operator, Craigslist, Facebook, Google, the list goes on. Just because driving a car seems different does not make it actually different.
There were reports that the actual procedures on the ship were extremely poor, and the quarantine was half-baked at best.
A lake has caught me off guard once before. But as a fully grown adult. I jumped in to swim a distance I could comfortably swim in the sea, but the slightly lower buoyancy I had in the lake caught me completely off guard.

I was hundreds of meters from the shore when I finally admitted to myself I was exhausted.

Made it back fine, but made me much more cautious about swimming in fresh water.
Ask HN: Is a startup with more than 18 people too big for TechCrunch?
Our startup (a distributed graph database, see nebula-graph.io if you want to know more details) has gained some attraction here on HN: https://news.ycombinator.com/item?id=22051271

So I am thinking maybe we can be featured on TC? I looked around the web for discussions and came across a post on Quora by an ex-CT folk:"Established company of 18 employees isn't "startup" feeling enough; seems too established. " The statement was made back in 2011, tho.

So I am just curious to know, is it just some personal feeling or a general rule of CT to pick up which startups to feature?

Any advice would be appreciated.
If the laptop is setup to route all traffic through the corporate VPN as many businesses do it doesn't just affect your home network.
> Research shows the annual shift disrupts sleep and leads to a higher immediate risk of heart attacks and strokes

The point is that the [bi-]annual shifting causes health issues, not which side of the shift we stick to
Are you predicting banks going insolvent?
> The best argument I've heard against DST is that it would put the kids coming home from school outside a sun-hour earlier, meaning there is more UV and it is warmer. That's a valid case against, seeing it's so bloody hot here in summer.

There are better arguments than that which have passed peer review:

* https://www.frontiersin.org/articles/10.3389/fphys.2019.0094...
It probably requires implementing marshal law.

Are you serious? Martial law (let’s at least start by spelling it properly) is not something you just throw out there and change a setting to disable once you’re done with.
Why is there a standard shell in POSIX? Because it is such a fundamental dependency, it saves a lot of trouble if it can be relied upon.
Note just that; the entire maps are showing present-day landscapes instead of ice-age landscapes. There should be glaciers, lower sea levels, and Doggerland.
Maybe not malicious but what he walked away with wasn't just Google's IP, I'm sure plenty of people working for / with him worked on that IP too...

There is a certain amount of disregard for other people who want to make cool stuff too IMO.
I feel the same way. Just scrolling down the history lesson to find the tldr
This article is really funny because it is true. I started programming C in 1987 and got my first programming job in 1992 (writing drivers for flash memory for windows 3.1). I was lucky to have a really good mentor. He beat me over the head to always use parenthesis whenever I used more than one binary operator and I never stopped. Sure, my macros looked more like LISP than C, but he burned the fear of god into me.
Have you considered the fatality rate and what would happen if it reaches the same percentage of population as seasonal flu?

Yeah, that would be bad, but there is no data to suggest it would get that bad.
The solution according to Hindu Mahasabha is quite clear

https://theprint.in/health/hindu-mahasabha-plans-gaumutra-pa...

These are not a group of random crank. These guys have a sympathetic and serious listener in the Indian government.

As an Indian all I can say is, "heaven help us", oh wait, they have that covered already.
Totally agree. I think it comes from people who have a narrow technical background trying to extrapolate to humanities by analogy to what they know. They only have a hammer and see nails everywhere.. But HN is the wrong place to expect anything different :D
As an architect, I am currently working on our org's first cloud deployment initiative. Due to federal compliance / regulations, we have no write access in higher / production boundaries, and everything is automated via deployment jobs, IaC, etc. Given the experience of the teams involved, I took the opportunity (burden) of writing nearly all the automation. If your architects can't handle shooting sick cattle in prod, I'd say get new architects.
I recommended avoiding Gitflow back in 2018:

> There are more complicated systems for branching like Git flow that have a separate “develop” branch and distinguish between “features” and “hot fixes”. These systems are fine if they fit your use case, but if a project releases code quickly, the level of complexity involved in Git Flow is unnecessary.

> Ideally, branches should be short lived. One strategy to allow merging a branch before a large feature is fully completed is to create a feature flag that lets the production system have the new code in it but in an inactive state.

https://blog.carlmjohnson.net/post/2018/git-gud/
Posts will be blurred after a predetermined period, two weeks for example, then users will confirm that they have met or talked on the phone to unlock their posts for another two weeks.
Tarsnap user here and I second your love of its pricing model. Business folks don't seem to like it though and prefer the bucket model. I think love for this model stems from an engineering mindset where we're happiest aligning our interests with our customers'.

I read about Michelin's case somewhere that I found interesting. Apparently Michelin doesn't sell tires to trucking companies - they sell miles. So they're incentivized to make better tires and miles is all their customers care about and they don't have to worry about whether Michelin is deliberately making bad tires just to make more money. Same "utility" logic here I think.
So then you create an executive order and then withhold federal funds from the states that don't comply. I wish states would have a backbone but with the lion's share of taxes going to DC they are just powerless.
Can you shield additional liquid assets by installing solid gold toilets in your Florida mansion?
Yes, it absolutely is different. The naive code will not have unwrap() in it, and it will fail to compile. At that point the developer can still mistakenly use unwrap() to unblock themselves, but it's still opt-in, not opt-out.

If you're implying that coders use unwrap() pre-emptively, I don't think there's any evidence for that. Besides, you can't just slap it on every value you have - it must actually be a result type! - so even if it's applied incorrectly in advance, that still requires some conscious consideration.

This is not at all the same as forgetting an "else" - or, far more often, forgetting the "if" altogether.
Yeah, that is exciting, we should all hope it turns out to be accurate. But by young, I just mean people age <60, not children. If 10% of the fatalities are people in their 20s, 30s, 40s, or 50s, that could be hundreds of thousands of people.
Do Not Touch Your Face
Yes!

The current consensus is that Homo Erectus left africa ~2million years ago. Homo Erectus were upright tool wielders, but were likely replaced by another wave of hominid from Africa - the ancestors to Neandertals and Denisovans - Homo Heidelbergensis around 500,000 years ago.

Ancient Eurasia had a variety of upright apes mostly originating from these. When Homo Sapien-Sapien, most probably both you and I's ancestors, left Africa (again in several waves between 40,000-70,000 years ago), they encountered, interbred with, and maybe warred with upright, almost human looking people, though the differences would be visible in the frame of the body and likely the face.

More info can be found here:

https://en.wikipedia.org/wiki/Early_human_migrations
The platform-provider relationship is a new thing.
A new kind of regulation is needed.

Trying to define drivers as employees or contractors is futile.