i always run mv -i to make sure i don't accidentally overwrite an existing file.

i don't alias mv to mv -i either, to avoid getting used to the idea that just mv is going to ask me, because i might work on a server where the alias is not set.

I double check the filenames instead, because many of the tools I work with don't have -i flags.

I’ve done

  gcc foo.c -o foo.c

far too many times :(

Seems like gcc should be smart enough to reject that mistake nowadays, right?!

I should write a shell frontend to gcc to warn if I do this…

I work in exactly two modes of `gcc` usage. I either accept `./a.out` as the name I deserve, or I write a `CMakeLists.txt`.

There nothing in between.