The Awesome Power of Self-Deprecation in ContentOps
I promise you that I’m going to make some grammar mistakes and maybe even factual errors in this post. Well, promise might be strong. But it’s quite likely at least.
The reason, dear reader, is that I simply don’t care enough to remedy that ostensibly bad situation. That, and the fact that I read at a 5th-grade level on a good day, combine to deliver you a wholly and unapologetically unpolished experience, should you read on.
The Inline Self-Deprecation Example
Real quick, let’s go meta.
What I just did there is something that I do all the time when writing, and I do it reflexively, without really thinking. I self-deprecate because it’s kind of fun, and come on, we shouldn’t really take ourselves too seriously. But beyond that, what I did actually serves a pretty significant purpose from an operations and efficiency perspective.
I neatly eliminated the need for at least one quality assurance step (and some person-hours) in my content production.
To wit, it’s now not super important that I have an editor take a grammar pass through this, nor that I find some flavor of SME to fact check. Why would I bother? I’ve already inoculated against the critique of “but you did a bad grammar!” and against the critique of “that is factually incorrect, sir!”
Imagine how stupid one of those comments would look in the comments section when I not only hinted at, but practically promised, those outcomes.
I didn’t need to pay an editor, and I didn’t need to pay a QA SME. I just needed to explain that I don’t care enough about those things to spend that time and money.