I often manually switch to the built-in mic of my MBP [edit: while using Airpods for audio output]. To switch more quickly, I found that when you alt-click on "Sound" while in the Control Center, you can select audio devices for input and output independently of each other.
> You do need to explicitly specify the other branch when merging or rebasing or making a pull request (like git rebase main), because git doesn’t know what branch you think your offshoot is based on.
I think a big issue with the presented intuition is that it's limited to wanting to merge the base/trunk/main branch into your feature branch. However, sometimes you want to merge a feature branch into another feature branch. With this in mind, you can form a better intuition, imo, where it's absolutely clear that you have to specify what branch you want to merge into another one.
It seems to me like this is only happening to articles from bigger publications. Perhaps because these publications have Medium monetization options turned on and this paywall is suddenly applied to all monetized publications as a "new feature"? Terrible, really.
There is an excellent TED talk on the relationship between self-worth and procrastination that also, like you, makes a point about separating "me and my work" [1].
Watching this about a year ago was eye opening to me and I wished I'd found this video when I started studying in college!
Something related I came to know only recently is that it has been shown to be more effective to floss before brushing teeth. I have been doing it the other way around my entire life.
- Tracked: Files that Git knows about. Further divided into unstaged files (will not be part of the next commit) and staged files (will be part of the next commit).
What helped me here was to know that it's possible to track a (yet untracked) file without staging it: