For good practices in writing high-reliability C, look at these:<p><a href="http:&#x2F;&#x2F;lars-lab.jpl.nasa.gov&#x2F;JPL_Coding_Standard_C.pdf" rel="nofollow">http:&#x2F;&#x2F;lars-lab.jpl.nasa.gov&#x2F;JPL_Coding_Standard_C.pdf</a><p><a href="http:&#x2F;&#x2F;www.leshatton.org&#x2F;MISRA_comp_1105.html" rel="nofollow">http:&#x2F;&#x2F;www.leshatton.org&#x2F;MISRA_comp_1105.html</a><p><a href="http:&#x2F;&#x2F;www.leshatton.org&#x2F;ISOC_subset1103.html" rel="nofollow">http:&#x2F;&#x2F;www.leshatton.org&#x2F;ISOC_subset1103.html</a><p><a href="http:&#x2F;&#x2F;www.embedded.com&#x2F;electronics-blogs&#x2F;embedded-systems-design-magazine-archive&#x2F;4216555&#x2F;Embedded-Systems-Design--May-2011" rel="nofollow">http:&#x2F;&#x2F;www.embedded.com&#x2F;electronics-blogs&#x2F;embedded-systems-d...</a><p>For the related topic of secure code, these books are good:<p>Mark Dowd. 2006. The Art of Software Security Assessment.<p>Robert Seacord. 2013. Secure Coding in C and C++, 2e.<p>For details on what is really going on inside C:<p>Paul Anderson. 1998. Advanced C: Tips and Techniques.<p>Kenneth Louden. 1997. Compiler Construction: Principles and Practice. Chapter 7.<p>For C gotchas and general good practices:<p><a href="http:&#x2F;&#x2F;www.cs.tufts.edu&#x2F;comp&#x2F;40&#x2F;reference&#x2F;CTrapsAndPitfalls.pdf" rel="nofollow">http:&#x2F;&#x2F;www.cs.tufts.edu&#x2F;comp&#x2F;40&#x2F;reference&#x2F;CTrapsAndPitfalls....</a><p>Allen Holub. 1995. Enough Rope to Shoot Yourself in the Foot.<p>P.J. Plauger. 1991. The Standard C Library. (It is partly a reference, but also has detailed discussion of the technical considerations faced in writing reliable code.)