yannick1976

There might be biases I’m not sure the study accounts for:

1. People who work remotely are more likely to have asked for it, and people who are in a situation that asked for are more likely to be happy about it.

2. People working remotely tend to fight for it, which makes them less likely to say bad things about it (such as, that they’re not happy with their work)

3. As another comment mentioned it, there might be a bias due to the fact that some jobs can’t be done remotely (e.g. housekeepers)

> The act of typing forces engagement

Nicely put

> large object promisors will work like this: - You push a large file to your Git host. - In the background, your Git host offloads that large file to a large object promisor. - When you clone, the Git host tells your Git client about the promisor. - Your client will clone from the Git host, and automagically nab large files from the promisor remote.

This doesn’t seem to solve the issue of the long download time / big repo size. Or is the author describing the use of promisors remotes in conjunction with partial cloning? Unless I missed something it is not stated explicitly.

On iOs, use two fingers to scroll through the cookies consent pop up to the Submit button :)