Since I like spaces around stuff I started putting two spaces after the infile at some point.

  < infile  x | y | z > outfile

I just didn't like how the filename was so close to the command name ;)

I'm in this camp as well, starting with input file redirection just makes so much sense to me.

    </proc/0/environ xargs -0

I also don't tend to want enormous volumes of text in my terminal scrollback so I generally view files or pipe verbose commands to `less`, then when I find what I want to send to the terminal I use the `|` less command to pipe it to `cat`.

Or to grab just a few lines for my later reference:

    kubectl get po/my-pod -o yaml | less
    /* find the lines I'm interest in */
    -N
    |^sed -n 34,35p

Oh `F()`. I should use redirection more with my Bash functions, and add it to my list (pun intended) of functional tricks [1].

[1] https://evalapply.org/posts/shell-aint-a-bad-place-to-fp-par...

This is by far the best explanation I've read for using that method. Thank you!