I almost always prefer to use what's available by default, that way what I memorize works anywhere.
But yes, for basic arguments, particularly for ls:
alias ls='ls -F'
alias la='ls -A'
alias ll='ls -l'
Occasionally for other commands for which the default is not ideal. w3m, for example, will read the bookmarks file if URL is passed, with '-B', but otherwise exits with an error, which is annoying. alias w3m='w3m -B'
Git commands, as others note.functions only for the complicated parts. about the same number of bash aliases as .gitconfig aliases.
pbpaste () { powershell.exe -noprofile -command Get-Clipboard }
pbcopy () { clip.exe < "${1:-/dev/stdin}" }
yt () { youtube-dl -fmp4 --no-check-certificate `pbpaste` }
None of these would work as aliases, unless you only want them to keep doing whatever they did in the first invocation every time thereafter. Eg: as an alias, yt would be limited to downloading the same video over and over again.
`$ alias` will show you your aliases, and it's a pretty easy command to remember ;)
alias aliases=compgen -a|fit
alias fit=column -c $(tput cols) 61
but yes alias command when I need to work on a system I aliased prior and have not used...