Converse is also true - if everything in the architecture can be a free-floating procedure, the system architecture will evolve around this.
2,465 karma · joined February 14, 2014
2a771933ef33b64a35c466ddc66d459eae1bbd62eec481c901f1316d60c13e32
It takes some time getting used to it. People say it's at least 2 weeks, but my experience is at least 2 months. I didn't know how to touch type before although I typed with 10 fingers. So in parallel I'm learning touch typing and getting used to a different layout (i.e. thumb cluster). When I passed 30 WPM threshold I finally started feeling comfortable and productive.
To me, biggest gain wasn't productivity but comfort/ergonomics! 80% of the finger pain was gone in 2 weeks. My shoulder and back posture is just way better. I don't slam the keys anymore, just gentle touch is enough to press them. I also "cheat" a bit by using Karabiner Elements with Space Cadet and Super Duper modes, and it's been a godsend.
To recap, it is expensive but I would never ever go back to any other keyboard :)
[0] https://ofdollarsanddata.com/why-buying-the-dip-is-a-terribl...
[0] https://ofdollarsanddata.com/how-to-invest-your-money-when-i...
You never rebase something into something else, you rebase onto something. I suppose you meant you want to rebase feature branch onto master.
If you have conflicts, you'll have them anyway, regardless if you're merging feature branch into master, merging master into feature branch or rebasing feature branch onto master. Conflicts are not a consequence of rebasing.
Proof: int main (int argv, char* argv[]), i.e. both parameters are called argv.
[1] https://www.justetf.com/de-en/find-etf.html?groupField=none&...
[alias]
cof = !git for-each-ref --format='%(refname:short)' refs/heads | sort | uniq | fzf | xargs git checkout
cor = !git branch --list --remotes | sed 's@origin/@@' | sort | uniq | fzf | xargs git checkout
cord = !git branch --list --remotes | sort | uniq | fzf | xargs git checkout