Sometimes writing shitty code is a result of competence, not incompetence. I've seen much better programmers than I ever will be writing terrible code because it was the fastest way to get a prototype running and find out whether the problem was worth writing good code for.
I love how it takes 2 comments to go from *Writing safe/good C code is really hard* to *Sometimes shitty code is good, actually*. In the context of using fuzzers to find bugs in existing code.