- Intensity Over Everything: You only do one main working set per exercise. That set must be pushed until you physically cannot move the weight for another full rep.
- True Failure: Failure isn't just when it starts to burn. It is the moment the bar stops moving even though you are pushing with 100% of your might.
- Quality Reps: Every rep should be controlled. 2 seconds up, a brief squeeze at the top, and 4 seconds on the way down. No swinging or using momentum.
- Recovery is Growth: You do not grow in the gym; you grow while sleeping and resting. Never train two days in a row. Always take at least 48 to 72 hours off between these workouts.
- The Goal: Every single workout, try to add either 1 extra pound or 1 extra rep compared to what you did last time.
A collection of useful git commands, because I'm lazy and can't be bothered to remember off by heart
scenario: free up space on your machine. delete anything that's been merged, no need to have it any more.
git branch --merged master | grep -v "\* master" | xargs -n 1 git branch -d- Plan to do the gallbladder flush over a weekend or when you have a couple of days off work to allow for rest and relaxation.
- During the week leading up to the flush, consume a diet consisting of mainly fresh fruits and vegetables, and avoid processed foods, animal fats, and dairy products.
- It's recommended to perform a kidney cleanse before the gallbladder flush, as Moritz suggests that congested kidneys can hinder the effectiveness of the gallbladder flush.
- Starting from the sixth day before the flush, drink four glasses (32 ounces or 1 liter) of organic apple juice each day. Divide the juice into smaller servings and drink throughout the day.
- The apple juice helps to soften gallstones and prepare the body for the flush.
| # delete all local branches that have been merged into master | |
| git branch --merged master | grep -v "\* master" | xargs -n 1 git branch - | |
| # amend a commit to the current time | |
| git commit --amend --date="now" | |
| # add empty git commit without adding files | |
| git commit --allow-empty -m "This will trigger a build" |
| function closestEl(elem, elClass) { | |
| var node = elem | |
| while (node.parentElement) { | |
| node = node.parentElement | |
| if (node.classList.contains(elClass)) { | |
| break | |
| } | |
| } | |
| node = node.classList.contains(elClass) ? node : elem | |
| return node |
| This post links my 3Box profile to my Github account! Web3 social profiles by 3Box. | |
| ✅ did:3:bafyreihaofdfkbrxqg73yvq36t3astt63owpfbtlheup5pup6hsh7d24nu ✅ | |
| Create your profile today to start building social connection and trust online at https://3Box.io/ |
The official way to install the flutter and its dependencies is a mishmash of brew install, binary downloads alongside relying on system installed versions of ruby.
I became particularly frustrated when trying to setup flutter on macOS Mojave and macOS Catalina. I came across too many issues, and it took a lot of stackoverflow and google searches to overcome.
By using a package manager to install dependencies and runtimes, we can share the exact same setup in different environments and automate the install and escape the above issues.
This is particularly valuable if you use different machines, or have team members in different locations. Moreover, we know where everything belongs and how to upgrade or uninstall if necessary.
| /* copied from an email */ | |
| /*The first piece we need is the Set object. This is one of the new objects available in recent versions of JavaScript. | |
| It’s something we don’t typically use much. The Set object is very cool because it’s a collection a little like an array, | |
| but it ONLY allows unique items. If we try to add a duplicate item to its collection, then it just silently doesn’t add the item. | |
| So if we give it five 3’s then it will only have 1 item in it, a single 3. | |
| The Set object’s constructor will take in any iterable object, which includes arrays. So we can give a Set an array, | |
| and it’ll load in the elements and any duplicates won’t get loaded. We do that like this:*/ |
| " Specify a directory for plugins | |
| " - For Neovim: stdpath('data') . '/plugged' | |
| " - Avoid using standard Vim directory names like 'plugin' | |
| call plug#begin('~/.vim/plugged') | |
| " Make sure you use single quotes | |
| " Plug 'junegunn/fzf', { 'dir': '~/.fzf', 'do': './install --all' } |