I used to think writing safe code in C/C++ was a matter of skill. However, after finding more than a few issues with AFL at a FAANG in code written by engineers with the highest engineering title, I changed my mind. Incredible tool.
It is a matter of skill to a certain extent though. A skilled programmer will write fewer bugs on average than an unskilled one. Nobody can write 100% bug-free code, independent of programming language.
I think it's mostly a testing thing. Valgrind is a friend a lot of people haven't heard of for c/c++. Setting up good regression tests is an art. Maintaining them is even harder.
I used to think writing safe code in C/C++ was a matter of skill. However, after finding more than a few issues with AFL at a FAANG in code written by engineers with the highest engineering title, I changed my mind. Incredible tool.
It is a matter of skill to a certain extent though. A skilled programmer will write fewer bugs on average than an unskilled one. Nobody can write 100% bug-free code, independent of programming language.
I think it's mostly a testing thing. Valgrind is a friend a lot of people haven't heard of for c/c++. Setting up good regression tests is an art. Maintaining them is even harder.
These are good tips, thank you