Also: enable all warnings the compiler offers and compile the code with different compilers (clang, gcc, MSVC - they all have different warnings), add copious amounts of assert checks, compile and test with the clang sanitizers enabled (address sanitizer, undefined behaviour sanitizer, thread sanitizer), and run the code through static analyzers (e.g. clang static analyzer and the one in Visual Studio), minimize dynamic allocation and pointer use.

With all those combined it's quite hard to hit segmentation faults and memory corruption and the source code will generally become "cleaner" and more robust.

This. I wish all C books had more chapters on this.

Not all the warnings, as many are not useful. But take -Wall -Wextra and see how that suits you and tweak it if necessary.

I really wish compilers had a -Wstandard and that warned on standard breaking things vs -Wall or -Wextra which has compiler specific junk like -Wparentheses

Perhaps -Wpedantic is what you want?

No, I basically want a W switch to warn only on potential buggy code (implicit-int, etc)