▲▼▲
This gist is a part of my public notes. Here's the "sitemap" of the notes:
flowchart TD
Notes -.-> Problem-based
Notes --You are here--> Observations[<strong>Observations</strong>]
Notes -.-> Logs
Notes -.-> Challenges
Notes -.-> Electronics
click Problem-based "https://gist.github.com/wzulfikar/ba2f58d7aeeb3cf53743316f96f91594"
click Observations "https://gist.github.com/wzulfikar/2cff9bcd64ba5f15296e0b57ff402f79"
click Logs "https://gist.github.com/wzulfikar/5ea5779d7f2ea0e27809e94e7904f93d"
click Challenges "https://gist.github.com/wzulfikar/7d5e9426d1c7efc3ceeabb29adb2f4fd"
click Electronics "https://gist.github.com/wzulfikar/16c3b5f10b8f28d8b0e325d03c948d1c"
Problem-based · Observations · Logs · Challenges · Electronics
Small Details ✨
There are small things I do quite often that I end up making a workflow around it. Here they are.
Alias
localhost
tol
.I often type
localhost:3000
in my browser when doing local development so I think it'll help if I make it faster. I added127.0.0.1 l
to my /etc/hosts file so I can just type l:3000 (much shorter!) in my browser, in terminal (eg.curl l:3000/api
), etc.Make git commands shorter
I often run git commands so I want to make it shorter. I made aliases so I can type
push
,pull
,co
instead ofgit push
,git pull
,git checkout
.Short commit message for minor, irrelevant changes
I often commit changes not directly related to the main goal of the PR but still count toward the work (eg. formatting, fix typos). I know the change is not interesting by itself and I know that I can still add comment in the PR if needed. For such commits, I use short message
f
. Combined with short git command from previous point, I can quickly push commit withcommit -m f
.Make shorter command when there's a pattern
I often use git and docker from command line and having some UI in terminal is very helpful, so I use
lazygit
andlazydocker
. I saw the pattern (lazy*
) and wrote more aliases to make it shorter:lgit
,ldocker
.lgit-ldocker.mov.mp4