skysight-inc/HackerNews huggingface dataset:
Well there are computational underpinnings to any form. Even those that are stochastic processes still have computational basis to some degree. So any cognitive process - which is quite literally the mind attempting to create form from various input signals - is going to be computable.

Wolfram's A New Kind of Science really changed my thinking about how we look at computational spaces.
I am using this as well for two smaller projects, it has been amazing. I tied it with Gitlab autodevops in about 30 minutes, most of which was dealing with migrating to DO managed Postgres.
I work for a rather large consumer goods company. We had a video taken down during a really important product launch. We had absolutely no idea why for three days.

It cost us maybe two full days of development resources + consultants + throwing money at different consultants to get an "in" to youtube to figure out why our video was taken down. About a week later we received official word from the artist and then we figured out that our consultants who made the video messed up and forgot the critical step of securing permission.

It was an expensive blunder, both from a media standpoint but also in the amount of resources we burned trying to figure out what the hell was wrong.

I'm not mad at youtube for taking the video down, but it's absurd that there's nothing in the system that would tell me why, and absolutely zero hope of figuring it out.
The issue isn't requesting a specific driver, the issue is a driver making a deal outside the app with passengers.

I seriously doubt drivers are allowed to make side deals with passengers.
Physician, heal thyself?
I mean before we had uber your exact case was often debated for the same reasons: Should agencies not have to employ you if you are solely dependent on them?
Yes, this is the general approach. However it unfortunately has security implications as you are putting MT workloads on a pool with access back to a shared control plane. Dealing with customer uploaded code is a nightmare.
What sort of repository and deployment structure are you using right now in which it works fine? I think that will influence the outcome a lot.

I just was working with a client that used something like git-flow, where develop was deployed to staging in order to test, master was always production, and the codebase is largely a monorepo. Then there were a couple other legacy repos, which also are using git-flow. It... "works", but it also is a needless source of pain. You need to PR to develop, then PR develop into master, and I'd inevitably get bitten with merge conflicts in the process. All that for what gain? I saw no upside to it. Maybe if you have steady release cycles, but git-flow never seemed to fit the whole disposable branches, master is good to deploy dozens of times per day sort of workflow I've gotten used to.
Sure but your example illustrates the key point of the article, your marriage is much like a two-person island. Which is great, as long as you two each are happy and well-matched. But it becomes hell as soon as the match is unbalanced. Stresses once managed by a community are now loaded more and more on two-person islands. If everyone turns all their energy into their two-people island and leave no room to invest in community, marriage all of sudden becomes too necessary for survival. Again awesome when you're well matched but the very definition of hell if you aren't.

Debatable if all that is true, but it does seem like the increasing atomization of society affects the nature of marriage.
Lots of downvotes. This was not meant to be a joke. I’m actually wondering if they will get sick pay now.
Deep Dive Analysis of a Killer Info-Stealer
I have some long-lived branches lying around for work I only occasionally have time and energy to do. E.g., I've an "ALWAYS DEFERRED" feature patch for PostgreSQL I need to eventually finish. Every time I come back to it I've fallen thousands of commits behind, and neither a merge nor a rebase can save me, but a rebase bisection script I have does save me by identifying the one commit upstream, in order, that causes conflicts that I have to resolve manually, then resumes the rebase bisection.

Specifically, the algorithm is something like this (not tested; I've a script I should publish):

bisect_rebase() {
local ultimate_target=$1
local target=$2
shift 2

b=$(git merge-base HEAD $target)
while [[ $b != $(git rev-parse $target) ]]; do
n2u=$(git log --oneline $b..$ultimate_target | wc -l)
n=$(git log --oneline $b..$target | wc -l)

# Try rebasing directly onto the target
git rebase --onto $target $b && return 0

# If we have conflicts and rebased across just
# one commit, stop here
((n2u == 1)) && return 1
if ((n == 1)); then
echo "Fix conflicts and exit 0 to continue or 1 to stop"
if $SHELL -i; then
git rebase --continue
return 0
else
git rebase --abort
return $?
fi
fi
git rebase --abort
bisect_rebase $ultimate_target $(git log -n $((n/2)) --pretty=%h $b..$target)
done
}
I find it amusing that in the course of chiding me for allegedly assuming laws are the same in all countries you assumed I'm American (I'm not).

I'm a taxi driver speaking generally about the differences in our job vs. Uber drivers. I will now step back and let the software developers argue about things they know nothing about.
What below minimum wage rates? In most of Uber's markets the price is based on supple and demand, and the drivers get a portion of that price. It's a market driven scheme where you agree to driving at that price. If you don't agree, then just change platforms, or don't drive!
True. As far as I know Jobs created almost nothing by himself but he was very good at recognizing and selling good things.
Indeed, now they can (but do not have to) require regular shifts.
Whup. Looks like a better article on the subject was already submitted.

https://news.ycombinator.com/item?id=22482862
Those numbers are very skewed though. Some categories have a lot more subcategories than others.

Like, if you split it up into long haul, short haul, in-town, etc, truck driver would fall down the list rapidly.
How does the electronic logbook tell if I'm in the bunk or in the seat? its smart, but not that smart.
> 100% strict adherence to git flow, which IMO is the wrong approach.

I agree, as with most things, there certainly is room for flexibility here.

One problem I've seen repeatedly occur when migrating to git flow is a misconceptions about 'bugfix/' branches, which are intended to be used when stabilizing a 'release/' branch. However devs use that prefix for every bug they find which is not related to a story/feature. And to be honest, they are right to do so. The naming is just bad here, since the term 'bugfix' is so generically used, it's not very intuitive to use it only for release branches. So I've come to the point where I would agree to use 'bugfix/' for regular bugfixing if the team/company is comfortable with it, even though it is opposed to original gitflow.
If I understand "base raters" correctly, they are not saying anything in particular about this virus, just that in general due to all available factors (including human+government intervention), the world generally stays close to the same.

A month ago, if you asked a base rater and an exponentialist to make guesses on how many cases in China there would be today, I think the base rater would be much closer to actuality than the exponentialist (after all, their new daily case volume stopped growing almost a month ago!).

China was able to pause this outbreak, maybe they can hold it, maybe the rest of the world can too. I'm not holding my breath but it does seem like a possibility.
I wish there was a "Preemptible" or more cost effective tier for GKE. I get why they're doing this and $70/month seems reasonable for a premium service but would be nice to have a more cost effective option similar with tradeoffs similar to "Preemptible" nodes.
BTW, I think there was a land bridge to Australia for a time, though not all the way to the Asian continent: https://en.wikipedia.org/wiki/Wallacea

It is perhaps unknowable whether someone went of exploring for years, then actually came back and got his/her remaining clan to migrate great distances. More likely that those migrations were multi-generational: the clan moved 20-50 miles every season following the game, and the descendants eventually got to a different continent.

However, there are examples of somewhat shorter distances in more modern times: I find it fascinating how the different cultures of Europe moved about: the Scandinavians to England and Normandy, later the Normans to Spain, Sicily, and Africa, the Slavs to the Balkans and Adriatic, etc. These are perhaps 1000 miles at most, but it seems like an entire warrior class and parts of the population went far away, conquered and installed themselves for generations in a foreign (and fully populated) place.
If a contractor just happens to work for you at some point of time for 8 hours per day, are they suddenly an employee?
Or move to minikube and friends. If it's a dev environment you can usually get away with such things.
With about 1/3 an acre I have a pear tree, two lemon trees, three apple trees, a nectarine, a nectaplum, a plum, two pomegranates, and a fig (there's also a redwood and various other non food producing trees).
I've got some grape vines started and a couple volunteer avocados.
Every year I grow a bunch of tomatoes, carrots, rainbow chard, kale, lettuce and other veggies.
I have rosemary, thyme, oregano, parsley, lavender all growing happily year round.
There's a couple guavas and other berry bushes maturing, not yet producing.
I have 6 chickens for eggs and they help me work through the compost.
Every day I'm eating something from my yard, one of the benefits of being in Northern California.
I dream about having a few acres but there's a lot you can do with <1.
Yep, you can already see it with the internet tax they are proposing. Well, European competitors like Bolt will prevail.
This has nothing to do with my point. Law exists to establish peace and consensus.

Contacts are the most basic construct enabling modern life in a crowded society.
Reinterpreting contracts in a liberal, unreasonable manner destroys peace and introduces chaos.

It prevents members of society from ever trusting one another, and makes all agreements tentative, subjective to the retroactive whims of politicians and court.

It serves the court, positioning it as an ultimate dictator, not the society.
Indeed, for small apps that average 2 instances or less during the month it's now cheaper to run App Engine Flex than GKE. Each instance costs about US$ 50/month in US central.

For those that are not aware, App Engine Flex runs services based on Docker containers with autoscaling similarly to Kubernetes. It has way less features than GKE, but if you are just running a standard app that only needs to connect to a database that is more than enough.

Bonus points: you can have multiple services, like back-end and front-end and make them available in the same subdomain - to avoid CORS problems. You can also host your front-end for almost nothing with App Engine Standard. It has an awesome CDN built-in if you know how to use it.
Linux desktop on your Android phone
Hi,

You can now run Debian Buster XFCE on a Xiaomi Redme 6 phone.
https://www.youtube.com/watch?v=REZ7fz81w_M

It runs as an application but requires root access.

If you own this budget phone you can try this out for free.

Vasant
If you like that did you also watch the one based on the book ‘Stumbling Upon Happiness’

https://www.ted.com/talks/dan_gilbert_the_surprising_science...

It seems to me almost like a scientific proof of Buddhism. This also made me really think about why I was perusing certain goals or not.

The basic premise is that humans think they’re really good at predicting what will make them happy, when in reality we totally suck at it and make lots of deliberate choices that are bound to make us unhappy.
Neither can a contractor build a gazebo for one client at the same time as they're building a gazebo for a different client. But there is a difference between getting paid for hours and getting paid for tasks.
Unannounced, somebody somewhere is building a caching service to preserve these “fleets” to sell them to whom ever is interested
Ironically you can take Via to the Waymo offices.
It's also not a favourable free market practice to protect inefficient jobs
> soul remediation.

That's the best pun - or typo - that I've seen in a while.
I actually read a great answer on Stack Exchange about it recently:

>In my opinion, any system that is used productively and is supposed to be maintained by people, should have documentation at reach of those people who are responsible for its support. The reason is, simply because:

Not all developers have the same IQ - You want every one to get it not only smart John.

Not all code is obvious, complex algorithms are not quite readable by all.

Business rules, while may be readable, may not alone show why they are there. Take for example this line in a reporting application:

if (lastname>="ZZ") then goto loop
it is somewhat clear to the reader what is happening but not why this is the case?

Finding out details take long time, it is a waste of business money.

Dependency between pieces of the system may not always be obvious. Especially in batch processes where each job looks like an independent program but the execution sequence is a package that must be processed according to certain rules (like monthly runs, etc.).

Documentation should help you understand logs and whether the results are correct or not.

When you understand the function of each component you can answer business questions. Say Suzan calls from accounting and asks why are we missing 5 checks this month? Some programmers may respond, well, I ran the job and gave me no error - This can't help Suzan. If you know which part of the system does the data extraction for processing the checks and then know what are business rules applied to qualify a check to be printed you can provide an useful answer - Assuming there were no bugs.

Remember that documentation go way beyond the comments that are inserted in code. They include ERD, Business Requirements documents, Design documents, etc.

In short: good documentation gives the developers the necessary control to maintain a system.

source: https://softwareengineering.stackexchange.com/questions/1217...
"In the old way of doing things, we treat our servers like pets, for example Bob the mail server. If Bob goes down, it’s all hands on deck. The CEO can’t get his email and it’s the end of the world. In the new way, servers are numbered, like cattle in a herd. For example, www001 to www100. When one server goes down, it’s taken out back, shot, and replaced on the line."

http://cloudscaling.com/blog/cloud-computing/the-history-of-...
Google are (were) not the only ones offering this free control plane model, though. My DigitalOcean DOk8s managed tend toward unstable if they are used with too small of node pools. (I don't know why that is, but it seems like a good way to make sure I pay attention to the workloads and also spend at least $20/mo for each cluster I run with them.)

It will be interesting in any case to see if DigitalOcean and Azure are going to follow suit! I'd be very surprised if they do, (but I've also been wrong before, recently too.)
Did you have any trouble with Uber over that or were you simply able to cancel with no drama?
I am not aware of Uber manipulating ratings of cancelled rides. From my understanding of the platform only riders can rate the driver. Is there a published policy that would back up either of our assertions?
How do you decide what to put on the wheels?
> I've also found it personally helpful to reframe failure as 'learning experience' and now you know more of what works and what doesn't (rather than a direct evaluation of some fixed ability), this helps embrace failure and growth without constantly doubting yourself or thinking that you may just not have the capacity to do what you want.

In fact, you can go further, and aim to fail. (Not in the sense of sabotaging yourself, but in the sense of doing things you're pretty sure are above your skill level, in the knowledge that you're unlikely to succeed at them, but are likely to learn from them.) Go in with the goal of learning as much as possible from the experience; and if you actually succeed, well, that's a pure bonus.

This is what Rejection Therapy is about, but it's also the basis of scientific positivism: you aim to prove the null hypothesis ("there is nothing interesting going on here.") Then you either succeed at proving that—and learning more about what hypotheses are worth making—or you fail to prove the null hypothesis, and instead discover some entirely-novel piece of knowledge about the world.
Congrats on the work!
Independent Tribunal into Forced Organ Harvesting from Prisoners in China [pdf]
Windows 95 UI Kit
Wouldn't flexibility be:

3) the freedom to set the terms and conditions for providing one's services.
Instagram followers and likes tools for free
Full-time driving jobs have existed for a century. There's nothing stopping people from driving FT if they want to, but they usually want the freedom and flexibility of working when and where they can that Uber is specifically designed for.

You can always come up with some scenario where it doesn't work while ignoring millions of drivers who are doing just fine. Would that mother in your example be better off without Uber? What if she can't work steady shifts every day and needs the flexibility?

People are perfectly capable of choosing what's best for themselves, they don't need the government to tell them what to do.
I have written a tool in go that will hopefully be helpful for many of you
Torrent Sites Help Game Developer to Share Free Copy of ‘Death and Taxes’
Complexity and politics by Dominic Cummings (2014)
> You learn what can throw, what cannot, and don't put exceptions in the hot path.

That puts you light-years ahead of most C++ programmers I've encountered.

> What does this mean? Are your objects in an object soup of interdependencies?

Not my code; other people's. We're talking about the typical programmer here, not the outliers.

> at the top, and along the entire path, you need to marshall error codes or change them....

Yeah, it's a pain, but that's totally not the point. Ease of verification and ease of later modification are orthogonal.

> The code is slower, has more branching, is harder to maintain (this adding bugs), than

"Simply handling..." How cute. What about proving that it's handled, not just sometimes but every time? What about the legions of programmers who "forget" to handle some exceptions? What about the dozens of aborted processes that I see every day while running one of the world's biggest storage services at a company famous for its coding interviews, that result from such sloppiness? Never saw so much garbage in the many projects I've worked on that didn't use exceptions.

Look, I'm not saying that return codes are all sunshine and roses. Neither are exceptions. I'm making a very specific point that exceptions make code harder to verify for either correctness or bounded performance, because somebody asked. Maybe you prefer exceptions and that's fine, but that's an advantage they don't have. These unfounded claims about non-exception code being so much slower or less maintainable (despite your own claim to write such code for high performance) add nothing to the conversation.
‘American Disruptor’ Review: The Life and Myth of Leland Stanford (2019)
Winterlight Labs | Senior Software Engineer (Multiple Positions) | Toronto, Canada | ONSITE | FULL-TIME | https://winterlightlabs.com

Winterlight Labs is a healthcare startup of 15 people that uses machine learning on speech to detect signs of Alzheimer's and other cognitive diseases. We raised our Series A in November 2019 and our clients include life science companies such as Pear Therapeutics, Alector and others. We use AWS for our cloud infrastructure and use modern technologies such as containization and infrastructure-as-code. Our culture is collaborative, friendly, and curious - we value people not only for their skills, but also for their opinions and experiences.

We have three positions open: Backend Software Engineer, Frontend Software Engineer, and Full Stack Software Engineer. Our current priority is to grow the team that builds apps and tools used by medical professionals to run our cognitive assessment. That said, we are always looking for excellent people. If you're interested, check out our careers page: https://winterlightlabs.com/careers
Yeah, I did the “JavaScript arrays” one. Don’t let the topic name fool you... They don’t show you everything up front. All those topics get pretty advanced.
Nit: we don't recommend dedicated nodes for isolation.
PTAL at https://www.youtube.com/watch?v=6rMGRvcjvKc
And the guidance from GKE is at https://cloud.google.com/kubernetes-engine/docs/best-practic...
Uber drivers can't pick up hailed rides anywhere. That has nothing to do with the jurisdiction, it's simply not a function of the app. If they did, they would be taxi drivers.
I honestly couldn't disagree more with this assessment of "stories".

Stories are great for the platform. They drive user engagement, and, hence, advertising.

As far as I can tell, they're terrible for the users. You have to constantly be active to not miss something, you can't just check back in after a few days. For some reason, comments are private only, which is almost never what I want -- as a poster, as a commenter, or as an observer. Contrast that with (say) a "normal" IG/FB post of a picture from the beach, where comments are public and a community of people and comment on it and reply to each other in a social way. Stories are basically broadcast-only. They're also MUCH more time-consuming to create.

I've only done a few stories, always when traveling solo, so I have time to kill and it was useful to learn something new the first time. The only positive thing I can say about them is that, because they're ephemeral, I feel less bad about posting some stupid snapshot of something unimportant/trivial.

That this is coming to Twitter is even more concerning, because it's already the most shouty, least-community driven social network, with the largest multiplier on saying trolling/annoying/controversial/stupid things in the pursuit of clicks and likes and retweets.
have autonomous cars really gotten so good that "what if violent criminals try to attack it" is the only criticism left?

No, they haven't. This is (by far) not the only criticism, but it's a valid concern which has literally zero attention to addressing it.

I'm pretty sure not hitting cyclists is still a much larger problem...

Probably, and that one still isn't fixed either.
The point is that none of this is going to happen overnight and though millions may suffer or die, there will be time for mitigation. Civilization won't end - which is the criteria for the doomsday clock. The inclusion of climate change may be well intentioned but it is inappropriate.
I don't know the answer, but one problem is that truck driving is already often a plan "B" (or "C", or ...), in that it provided a practical home for workers displaced from other industries. Often one they didn't have to move to get.

This has difficult implications if you are looking for things these folks can do instead of trucking.