hhsuey

TIL...

25 closed merges, of which half of them are closed and half merged. Compare that to 330 forks and 6.7k stars. This is still an overwhelmingly read-only parent fork that is basically the author's personal TIL blog. https://github.com/jbranchaud/til/pull/24

Apparently the oldest fork wins, or the author of the repo can decide. https://webapps.stackexchange.com/questions/86769/which-fork...

Would you say you've done a lot of projects though and that was the win itself? And that despite not being able to find a purpose to most of the projects, the benefit has been the learning/growth/experience/fun/etc...?

Deleting a private repository

When you delete a private repository, all of its private forks are also deleted.

Deleting a public repository

When you delete a public repository, one of the existing public forks is chosen to be the new parent repository. All other repositories are forked off of this new parent and subsequent pull requests go to this new parent.

Why would you need to create notes and go back to it though? Isn't searching for it much faster? Say you learned a nifty hotkey to backup text using a shortcut on OSX (or whatever). Why not simply search "hotkey backup osx"? And say that page you found it on shows up, but like you said, it's very long text page. Then just just bring up the search-in-page feature in your browser, and you're there!

Isn't that just a blog or a subreddit? And couldn't you find all the TIL blogs by Googling for "TIL" or something?

Sorry, good work to the author. I'm kind of a downer, and personally struggling to find motivation to work on projects, but often shoot myself down first. I don't see the point in a lot of projects out there.

Makes sense. I thought about it a little more and came to the same two potential reasons.

Gotcha. So the motivating factor was for individuals to get a copy for themselves, perhaps even use it as a form of bookmark overloaded as a backup feature. They'll need to keep pulling if they want to keep it up to date, but I suppose that could be automated.

I don't really see the point of this, except that it helps the author stay consistent to make updates and learn things. I'm not really sure why anyone would consume this, except for curiosity into what they could do for implementing their own consistency forcing function.

Forgive me for my ignorance, but I haven't contributed to open source much yet. What is the reason for forking this repo. I see a lot of people have done it. Wouldn't that be akin to cloning someone else's personal blog? I just don't see the point of that.

The correct model is that of bacteria in a petri dish. As long as you have a few bacterium left, they can regrow. And as long as we're getting reports of a few cases in major cities or countries, those cities or countries will lock down. So it doesn't matter how many bacteria are left as much as how long it takes to get the last remainder eliminated.

That's ridiculous. With that logic, if you're supposed to save X months of cash, then the very first cent you take out of that X months of cash savings, you already fucked up, b/c now you have less than X months of savings. Suppose you wanted to overcome this. So then you decide to start working a second job so you never have to touch the emergency savings. Then that defeats the entire point of the emergency savings, which is to be used when there is an emergency.

The company could also be said to be fucking itself over if it can't have enough cash to prevent layoffs of necessary employees. If it doesn't have enough cash at hand, it will need to lose talent and be forced to try to rehire when the economy rebounds. A competitor with a good savings account could instead leap past b/c they could simply dip into their savings and continue to build for the rebound, with all their engineers on board.

Unless, the definition of fragility for a laptop is different than that of say a basketball. The former is expected to not be dropped, while the latter requires it.

I feel like this is what an engineer who doesn't really understand businesses would write. The models he writes about don't even come close to the complex realities of politics, externalities, market factors, accounting, funding, etc... When he started talking about workers like cpu cores, I knew immediately, this is not going to go anywhere.

My advice would be to define in multiple realms what you consider to be strongly focused, while both realizable and healthy in the long-term.

Taking a math course that attempts to teach some of the ways mathematicians approach their profession, which I hear is quite different than learning math or doing math the way it is taught in schools or utilized by other types of professionals (e.g. engineers). The class is called "Introduction to Mathematical Thinking" by Keith Devlin, and it's on coursera.org.

"why does our team exist" is a rabbit hole for me. It goes to "why does our company exist" to "why does this industry exist" and "what am i doing with my life" and why does any of this matter".

Can you elaborate? I found the description of the two quite fuzzy.

> Rather than focusing on a list of things other developers have learned, and targeting that list, I humbly propose that a leading indicator of acquiring this kind of knowledge is “hours per week spent in a state of intentional deep work”.

So he's just proposing that one should just spend time to cultivate those skills?

> Imagine two equally knowledgeable early-career software developers. They have the exact same skills on January 1, 2020. If the first software developer spends four hours a week doing deep work, while the second software developer spends fifteen hours a week doing deep work, their trajectories will be quite different, and that second developer will quickly gain technical knowledge and proficiencies.

This isn't rocket science. Just spend time developing skills in addition to the work you have to do already. Great!

> Utilization, the percentage of a worker’s maximum available working capacity, increases indefinitely as the request queue builds up, resulting in a utilization graph like this.

Keyword indefinitely. Isn't this assuming the service worker doesn't have a timeout itself?

Also, the neighborhoods tend to be safer and more inviting than those right next to the major freeways.

I was originally thinking air quality is the major reason, but Vancouver has really good air quality overall compared to where I live in Los Angeles. I would be interested in seeing this type of study be done across cities with different air quality.

We say "arse" here to be less crass.

It's the only benefit I suppose.

I neglected to think about tab-completion, but I see you mentioned it at the end. I've never used it for bash. It really depends on whether I can guess or remember the first letter(s) to the option. If it's a command I am new to, I'd still need to print out the available options anyways.

I think bash is terse for at least 2 reasons:

1. Quicker to type repeated variations of commands at a CLI.

2. Memorization of flags isn't as much a concern since you're at the CLI, you can often easily look up the meanings of options and flags with -h or man pages.

It may be slightly more difficult in the beginning, but once you're familiar, terseness saves significant time.

I would relate shell languages more to vim or emacs in that regards. They have a higher learning curve but pay off in efficiency in the long term.