| // ==UserScript== | |
| // @name Absolute Enable Right Click & Copy | |
| // @namespace Absolute Right Click | |
| // @description Force Enable Right Click & Copy & Highlight | |
| // @shortcutKeys [Ctrl + `] Activate Absolute Right Click Mode To Force Remove Any Type Of Protection | |
| // @author Absolute | |
| // @version 1.8.9 | |
| // @include *://* | |
| // @icon https://i.imgur.com/AC7SyUr.png | |
| // @compatible Chrome Google Chrome + Tampermonkey |
How should we decide what actually to work on in order to more effectively achieve our goals? Assess the activities' leverage:
Leverage = (Impact Produce) / (Time Invested)
Another way of thinking about leverage is the commonly-mentioned Pare- to principle, or 80–20 rule—the notion that for many activities, 80% of the im- pact comes from 20% of the work.
If you use git on the command-line, you'll eventually find yourself wanting aliases for your most commonly-used commands. It's incredibly useful to be able to explore your repos with only a few keystrokes that eventually get hardcoded into muscle memory.
Some people don't add aliases because they don't want to have to adjust to not having them on a remote server. Personally, I find that having aliases doesn't mean I that forget the underlying commands, and aliases provide such a massive improvement to my workflow that it would be crazy not to have them.
The simplest way to add an alias for a specific git command is to use a standard bash alias.
# .bashrc| // Alternative JavaScript Syntax | |
| Person = :(name, address) { @name!, @address! } | |
| Person::inspect = :{ <: "{@name} lives at {@address}" } | |
| tj := Person('TJ', '314 Bessborough ave') | |
| bob := Person('Bob', 'Some place') | |
| [tj, bob].each(:(person){ print(person.inspect()) }) |
