Seventeen steps to safer C code

Thomas Honold had share his view in having a safe C applications. He listed out 17 steps and discuss briefly with sample all the steps [Article].

It is a good article, but there is nothing new in this except its implementation in an embedded environment. The steps was known since late 90s after chaotic event caused by insecure C applications. The issues here is not the steps or C, but the mentality of developer/programmers whom ignore security implementation for the sake of speed in processing or faster development. This is something need to be changed.