What do you want me to write?

To meet the bar set by onlinepersona, you'd need to write safe C code, not just some of the time, but all of the time. What you appear to be proposing is to provide evidence that you can write safe C code some of the time.

It's like if somebody said "everyone gets sick!", and some other person stepped up and said "I never get sick. As proof, you can take my temperature right now; see, I'm healthy!". Obviously, the evidence being offered is insufficient to refute the claim being made by the first person

Can you point to relevant non-trivial public work of yours that has zero CVE's?

The more you learn and know, the more you refrain from making such statements. This is universally applicable, and not limited to C or programming. And that's what makes your "story" suspect.

Or maybe it's a reading comprehension issue.

^I^ ^used^ ^to^ ^write^ ^non-trivial^ ^C^ ^code^ ^myself^ ^btw.^

I want you to write kernel code for a few years. But we go to Lemmy with the machismo we have, not the machismo we wish we had. Write a JSON recognizer; it should have the following signature and correctly recognize ECMA 404, returning 0 on success and 1 on failure.

int recognizeJSON(const char*);

I estimate that this should take you about 120 lines of code. My prior estimated defect rate for C programs is about one per 60 lines. So, to get under par, your code should have fewer than two bugs.