- People are more likely to follow through with something if they can visualize themselves doing it (SOURCE.)

- The value of ai is not what it performs, but how it is programmed.

- Most people when given the opportunity to learn their passions will grow in a way that benefits all.

Git stash is a command that temporarily shelves (or "stashes") changes in your working directory so you can work on something else, then come back and re-apply them later.

Stashing saves: Modified tracked files and staged changes (unstaged changes by default, staged changes with -u flag) Doesn't save: Untracked or ignored files (unless you use git stash -u or git stash -a).

- git stash save "WIP: feature implementation before switching branches"

- git stash push -m "descriptive message here"

- git stash list

- git stash apply

- git stash pop

- git stash apply stash@{2}

- git stash show -p stash@{0}

- git stash drop stash@{1}

- git stash clear

- Always use descriptive messages: git stash save "fixing auth bug - half done" instead of just git stash

- Check stash list regularly: git stash list shows all stashes with their messages

- Apply to branches: Create a branch from a stash: git stash branch new-branch-name stash@{1}

- Use apply not pop initially: apply keeps the stash so you can recover if something goes wrong

- Clean up old stashes: Review and drop stashes you no longer need to keep the list manageable

git stash save "WIP: dashboard refactor"

git checkout main

git checkout feature-branch

git stash list # Find your stash

git stash apply stash@{0} # Or git stash pop if you're confident

LLM.: Stashes are stored as commits in your repository's object database, so even if you accidentally clear them, they can sometimes be recovered using git fsck --unreachable within the reflog retention period.