Unless it's documentation, I don't do major revisions

That's right! I don't do major revisions once I publish something. Once it's out there, I move on to the next project. The only exception is technical documentation. By nature, technical documentation is fluid because it's contingent on the product or service it documents. So if there's a major update to a software, I would expect major changes to the documentation. Even with minor software updates, depending what's changed, I would expect changes in the documents too.

We technical writers are constantly writing, editing, and revising materials when we're actively working on projects. Some may call it a curse. I call it a blessing because we get further use and hone our craft.

So my rule of no revisions doesn't apply to technical writing or technical documentation. I'm talking about published works outside of this realm. 

Erases Your Growth

When we go back and do a revision of work we've created and published, it erases the growth we've made as writers. (I'm not talking about works that need periodic or regular editions. In those cases, you would need revisions to keep your material relevant or accurate.)

My earlier work isn't good. So what! While I still don't believe I'm a good writer, I've seen continual growth since I dedicated myself to the craft.

Growing Since My Novel

When I published my novel The Unlikely Messenger in 2019, it was a feat. I was in knots whether it was good but I pulled the trigger to get it out. It was sitting somewhere tucked away for years. My thinking was if I wrote something and I'm okay with it, then why leave it unpunished?

I'd probably cringe if I looked at my novel again. It's been a while. I know I've changed since then, especially in matters of eschatology. I've also tried have a more consistent Christian worldview since then, though I still have a long way to go.

Would I write a dystopian novel again? No! While tyranny, evil, and injustice is rampant, dystopian societies don't last for the long haul. They either end in overthrows or implosions. History shows they always go into their dustbins where they belong. So if the powers that be managed to create a one world government, it would be destined to fall apart. Even if God doesn't intervene, people's egos, especially those in power, will make it implode or nations would break away anyway after getting tired being told what to do.

But would I go back and make revisions to my novel? No! For if I did that, it would no longer be the story that I wrote. I'm okay with the follies, blind spots, and probably bad writing that's in there. It's a benchmark for me to know where to go from here.

I Let Blog Posts Stand, Well Mostly

I don't even go back and revise my blog posts either. If I went back to say it better, then it would no longer be the posts that I've made. The only exceptions would be spelling and grammar errors or a factual error if I notice. Besides that, the posts stand.

Cancel Culture Nullifies Progress

The cancel culture is beyond ridiculous because it doesn't allows us to be humans. Are there stupid or evil things we all may have said or done? Yes! No one is above this folly. Let's discuss them honestly. Let's own up to them. But to cancel people for what they said or written years ago even they don't believe those things anymore, and even now repudiate those previous beliefs, negates their growth. Those past errors and evils are there for us to learn from. (I'm not talking about people that are still doing and saying stupid and evil things.) If we erase or cancel them, then we're more apt to repeat the same evils or follies because we'll no context or history to move forward from. 

Be Careful about Embracing this Mentality

Be careful about embracing the cancel culture. If we're going to be consistent with embracing the cancel culture, we have to erase everything, including ourselves. As Jesus said, be careful about the measure we use for it will be used against you.

Any writer worth their salt should understand the danger of the cancel culture mentality. This mentality will destroy vigor in all writing, including technical writing. I'm glad people have pushed back on it. I hope this absurdity goes into its dustbin. I digress.

Don't Erase Your Mistakes

The easiest way to hit a plateau where your writing becomes sterile is where you're obsessed with erasing imperfections. How will you know that you've grown and progress as a writer, if you can't embrace your earlier mistakes? Accept that you made them. Learn from them and move on. 

Be Human and Understand the Journey

We as writers must be at peace with what we put out, even if it makes us cringe. I still cringe at earlier technical documentation I've written, even if it was a short time before.

Seeing the progress you've made as a writer is far better and more rewarding than trying to have everything look and sound "perfect."  That sounds boring and machine-like. Be human. Understand we're all on a journey as writers. 

Writing for Validation? No!

There are many reasons to write. But there are reasons not to write. Validation is one.

If you're writing to seek approval, then you're going to be disappointed. While it's crucial for writers, especially those of us who are technical writers, to build bridges with the audience you're trying to reach, you're not going to find validation from them. 

The audience doesn't care who you are or what you write. Ultimately, they're just looking for information and content they want and they move on once they get it. If they return, it's because they're looking for what they want, not you. Now, some may counter me and say they like certain writers. Is it the writers themselves they seek, unless you're some nut job stalker, or stuff they write? You know the answer to this question.

If you're looking for approval with your company, good luck with that too. You might get some unsolicited advice if you're constantly asking Subject Matter Experts (SMEs) whether your writing is any good or your documentation has any value. They'll let you know if they're not happy.

Taking constructive criticism is one thing. We need it to improve as writers. Writing is an ongoing process. We only get better by doing it constantly and humbly taking feedback. Heck! You can even send surveys to your audience and the SMEs to see how you can improve documentation. After all, documentation is about serving your audience. But seeking validation is another. It's an unhealthy extreme. Validation is a phantom prison!

You're afraid of what others think and you ruminate about the possible criticism or some half-cocked comment from someone. So, you try to appease them and you lose your voice in the process. But in reality, they're not even thinking about you at all.

The fatal problem with seeking validation is it makes you the center of the universe.  But guess what, you're not the center. 

Seeking validation is in the same vein as comparing yourself to others, but it takes it a step further into narcissism. What one really wants is accolades and praise? What someone who seeks validation wants is an echo chamber. Let's be honest. Do any of us go around seeking to find criticism, even if it's constructive? No! We prefer to do things our way. I'm not saying that's right. I'm just saying that's what we tend to do.

So why seek validation for your existence as a writer, particularly a technical writer. Let's keep our heads down and power through to great documentation. Leave the rest up to God. Seeking validation is a big waste of time and energy. Don't do it! Be humble yet confident in your abilities. But if you're writing only because you want the approval of others and want people to extol you, then maybe you shouldn't write at all.