The author linked to this site: <a href="https:&#x2F;&#x2F;www.securecoding.cert.org&#x2F;confluence&#x2F;display&#x2F;c&#x2F;SEI+CERT+C+Coding+Standard" rel="nofollow">https:&#x2F;&#x2F;www.securecoding.cert.org&#x2F;confluence&#x2F;display&#x2F;c&#x2F;SEI+C...</a><p>These are wonderful. Concise nuggets of knowledge that you can keep in your head, little warnings of what not to do.<p>Side note, it&#x27;s really fun reading this article about modern C given that I&#x27;m working on an experimental programming language meant to replace C [1]. Just today I got the Guess Number Game example working, without a dependency on libc [2] (caveat: Linux x86_64 only so far). So, I&#x27;m having fun trying to think about how C could be better, reading implementations of various libc functions, and writing my own &quot;standard library&quot;.<p>For example, in my language, there are no `int`, `unsigned char`, `short` types, there are only `i32`, `u8`, `i16`, etc (I shamelessly stole this idea from Rust). This mirrors the article&#x27;s suggestion to only use int32_t, uint8_t, int16_t, etc. But, since it&#x27;s a new programming language, we don&#x27;t have the other types sitting there as a red herring.<p>[1]: <a href="https:&#x2F;&#x2F;github.com&#x2F;andrewrk&#x2F;zig" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;andrewrk&#x2F;zig</a><p>[2]: <a href="https:&#x2F;&#x2F;gist.github.com&#x2F;andrewrk&#x2F;131e6f48a15c42fc5ca8" rel="nofollow">https:&#x2F;&#x2F;gist.github.com&#x2F;andrewrk&#x2F;131e6f48a15c42fc5ca8</a>