Don't Trade Your Passion for Glory

There's a line in the song "Eye of the Tiger" by Survivor where it says:

You trade your passion for glory

This song speaks volumes of truth about perseverance, which is the only way to get better. But for this post, I'm going to focus on this line. We must be careful not to trade our passion for glory. If you seek to glorify yourself, you will lose the reason why you got there in the first place. It's far better to keep your passion alive and labor away in "obscurity" than to get accolades from others and in the process your passion dies. And when passion dies, you lose the core of your craft.

Glory is a Siren. Though she calls in a seductive voice and she is beautiful, don't go and embrace her or you will "die." It's too easy for us technical writers or writers of all stripes or anyone else for that matter to get drawn in by her songs. Resist her! She is fleeting. People are fickle. One moment, people love you. The next, they revile you.

There's nothing wrong with success. If you worked hard and got there honestly, then God bless you for it! Don't beat yourself when you're successful. But be on guard! Make sure you don't let the glory get to your head, you become arrogant and dismiss those who helped you along the way.

Passion may not at first look as beautiful as Glory. But if we look again, Passion's beauty is deep within and shines through. 

Glory only has the surface beauty but her heart is hollow. Passion is full of simple and pure innocence. Passion will be there and she inspires you to persevere and to be creative. Glory will fade away and move to another when the winds of trends blow her toward another direction. So hold onto Passion. Let Glory go!

For Passion is a faithful soulmate. Glory is a perpetual adulteress.

Passion survives. Glory dies.

Without growth and conflict, there's no story, even for technical writers

They say without conflict or growth in a character, there's no story. But why? Is this some tired trope or does it apply in real life? Well, let's walk this through. Is there a story when you're just going through your daily routine or when you're having choose between two great job offers? Is there a story when you're ready to get married but an old flame, whom you loved dearly, showed up? What makes even more interesting the reason for your breakup was a simple misunderstanding. Stories aren't just in the realm of fiction. Stories happen all the time in the real world! Why do some people read biographies, autobiographies, memoirs or historical accounts? They deem them to be worthy stories to read. 

Even the Bible, though I fully believe it's God's Word, has elements of story. Here are a few examples: 

• When God tested Abraham and told him to sacrifice his Isaac in Genesis 22. (Thankfully, there was a happy ending to this.)
• The story of Joseph and his brothers in Genesis 37-50.
• Joseph (different one) found out that Mary, who we was engaged to was pregnant and he wanted to divorce her quietly in Matthew 1:18-25. But he was informed that baby was the Promised Messiah, Jesus.
• When Jesus knew His death was near, He ask God, His Father, for Him not to go through it in Matthew 26:36-45, Mark 14:32-42, and Luke 22:39-46.

As conflict and growth of characters are essentials to crafting a good story, I believe these same elements are essential what makes us become better technical writers. How? Well, here are a few examples.

Let's say you're dealing with a difficult SME and you need to deliver some documentation by the next release, which is around the corner. This SME is hard to reach or gives little to no information on crucial parts for the information. So what do you do? Well, you either find a better way to reach this SME or find other key people who can help you get this information. To boot, you get this information at the last minute so you have little time to create quality documentation in the process right before release time.  Doesn't this sound more like a story than dealing with an easy SME, who gives you exactly what you need and when you need it to create the documentation and you're done way before it's time?

To be frank, I like it when there's no drama and I'm able to get everything I need to create a document without issues. I suppose I could say the story is everything lined up exactly as planned. But that's somewhat of a rarity in our line of work. Eventually, this stops becoming a story and morphs into a routine. Where's the growth or conflict? I don't like any conflicts either, but we live in a broken world, so unavoidable. But brokenness births countless stories. This is my problem with those who looking for a "utopia" or demand constant perfection. If we got what many wanted, stories will cease. 

Since conflict is inevitable, it's about knowing about how to find good resolutions to them. That's another key element in what makes a story. Who wants to read a story, unless you're an Eeyore, where there's no satisfying ending. Even open endings can be satisfying, if they're good. 

I'll share a time where there was conflict, resolution, and growth that came from it.

My Story: Creation of a Style Guide

When I was working at a company, the SMEs would fight me and the other technical writer on how to write the documentation. The SMEs wanted to write in passive voice instead of active voice. They also wanted to write "the user" when it was a clear case of writing "you", which was their audience. But to be fair to them, in my zeal for clarity and style, I would in some cases inadvertently change the meaning of the content. (This could have been avoided if we were given access to test the software but that's another topic.) 

We constantly battled over which words and phrases were correct, instead of focusing on releasing the documentation with the software. This fight drained the SMEs and us. The head of the company had to mediate in this conflict. After hearing both sides, he suggested that we technical writers create a style guide. So me and the other technical writer went to work to create the style guide. We used different sources, such as "The Elements of Style", to help us craft our tone and voice for the documentation. 

After much discussion and iterations, we were able to create a style guide that would help direct us and the SMEs on how the documentation would sound. It wasn't perfect, for no style guide is, but it reduced the fights to nearly zero. Those who wanted to fight still, we would just refer them to the style guide and the directive we got from the head of the company about this. 

We both became better technical writers from this. Though at that time, I hated going through every bit of this. I look back and thank God that this happened. If it didn't, I wouldn't have grown as a technical writer.  I learned to better balance clarity and style, while retaining the original meaning of the SMEs intended. By having this balance, the intended audience will get clear and accurate information. This is not to say I've perfected this, but I constantly strive for this balance whenever I create documentation. I've also learned to ask better fundamental questions to better get this balance. And when possible, I ask for ways for me to test what I am writing about. Before this conflict, that wasn't on my mind. 

I have to constantly remind myself conflicts can bring growth. It's too easy to wish a life without problems. Let's resist this silly (quite frankly, unbiblical) thinking. Without conflicts, there's no story. Without story, there's no life. Without life, there's no world.

Clear Writing is Crucial to Using AI

This post is an addendum to a previous post. Though I'm still not afraid of AI, I've come to terms it will alter the landscape of what we do as technical writers. With the launch of Grok4, despite the controversy that surrounded it, this reaffirms AI isn't a passing fad. Those who think otherwise are living in a fantasy land. Unless there's some grand event that causes technology to cease, there's a mass rejection of AI, or even a bigger innovative leap, it isn't going away. But despite how powerful it is or how it will get, AI is still a tool and it's a tool that we need to master. So how do we do this as technical writers?  We focus on writing clearly. 

If or when we need to use AI to help us create documentation, we'll need to use AI prompts. In those prompts, it will be key to write clear and specific instructions. We can lay this out how we want the documentation to look. Of course, we will still need to writing the content itself or we should. Using AI isn't an excuse for us to shirk our duties as technical writers. If anyone does this, I'm absolutely against it. Documentation will always need human nuance to make it good. So we still need to do the hard work!

One of the nice things about using these AI prompts is that we can constantly refine our creation so it will eventually match what you're looking for. Or, it might even exceed our expectations. Of course, it can become a problem with when you're using a free version of the AI. Waiting another day after you past the message limit to clear isn't always ideal, especially if you need get documentation out for an impending release.

By focusing writing in clear, specific, and concise instructions in these prompts, it drives us back to the heart of the technical writing style. In a weird way, it takes us back to good ole technical writing.

Is it a possibility that AI will eventually make technical writing disappear? Don't know. Only God knows the future. I may have still concerns with AI but it's not going to take over, if we don't let it. What I do know is new opportunities will arise when old ones die. We no longer have milkmen but we do have refrigerator repair technicians. Just keep on writing. If you need to use AI, then make sure your voice and skillset still shines. I think I'm with this topic for now.

Why I'm Not Afraid of AI

AI. Artificial Intelligence. It's either met with excitement or with fear. In any case, it's been the conversation piece for many. My understanding of AI has grown since I've first wrote about it. But this post isn't so much about AI. (There are plenty of experts out there who can tell you all about it.) My post is focused on why I'm not afraid of AI.

Tentative Stance

Before I get into why I'm not afraid of AI, here's my tentative stance: Artificial Intelligence isn't some nefarious overlord or a cabal of overlords plotting to dominate or exterminate humanity but it's also not some passing techno-fad that'll vanish anytime soon. Think MiniDiscs.  If we think about it, Artificial Intelligence has already been with us for some time. Think spelling and grammar checkers or chess super computers.

Because of its seemingly endless potential, like the Internet, Artificial Intelligence continues to transform and help us find better ways to do things. But in the process, this might include making certain jobs obsolete. Sadly, this happens with every technological innovation. But only God knows the future, so AI's continued existence is yet to be determined. Since we're in the present, we need to face AI and know how to move forward with it.

AI and Writing

AI may be able to correct spelling, grammar, and write text. It might be able to produce huge tomes. But I don't think it'll take over documentation and make technical writers obsolete. I'm not afraid. Why? Documentation. Well, good documentation needs human nuance.

Human Nuance

What do I mean by human nuance? And why will AI never replace it? Human nuance is just discernment. It's been able to go beyond the surface and dive deep and note the differences. No matter how advance AI becomes, it won't fully know what to include or leave out in documentation. When it comes to writing, it can't do what Mark Twain said. Only a competent writer knows how to do this. Artificial Intelligence also won't fully know the audience, so its aim will be off when if it writes documentation. Algorithms can be helpful but they fall short. Only a technical writer or an SME, especially those who talk to their customers, truly know the audience. 

AI also won't fully know how to structure the information in documentation.

Good documentation goes way beyond well-crafted prose. (If that were true, AI could replace us technical writers. But that's not the only factor for good documentation.) What can make or break a document is how you order information. You need a logical or natural order to make a document flow. Let's not forget one more ingredient to documentation: creativity. There's always an element of creativity involved when designing documents, especially when it comes to its flow.

AI can't do any of this. Why? It's not human. We're humans and write for humans, not for machines. We write to humans to show them how to use a tool, software, or machine.

AI is just a Tool

AI is a tool. It doesn't matter how powerful it's becoming, it's still just a tool. This is no different than huge tractors or industrial drills. They're powerful and have allowed us to do far more than before they were created. But despite their power, they're useless if no one wields them. The same goes for AI. If no one uses it, then it'll just sit there. It doesn't matter how it advanced as it continues to evolve. It's just a tool–a useless one at that if no one uses it.

How ridiculous does it sounds to run away from hammers, screwdrivers, and power saws because we're afraid they're going to replace us. So why do some have this kind of fear with AI?

You can laugh and say I'm naive or I've drank the Kool-Aid (actually Flavor-Aid) of the technocrats who are pushing Artificial Intelligence. No! Quite the opposite! AI is overrated! It's powerful but it's just a tool! So, it has no power if no one uses it.

Rather than running scared, thinking it's some virtual, evil demon who seeks to master us, we should grab a hold of AI and make it submit to us to do what we need it to do! Rather than getting worried whether Artificial Intelligence will replace us technical writers, if the AI revolution continues, let's use it in our favor to augment our abilities to create good documentation.

Could AI cause a lot of harm and destruction? Yes! Absolutely! But so can cars and knives if they're wielded by very bad people. Since AI is just a tool, it matters how you use it. So, if someone misuses it, don't blame the tool. Blame the user! 

Also, letting AI run unchecked is a bad idea. That's like just leaving a wood chipper on! It shouldn't take much imagination to foresee how many problems can happen there. You don't leave tools on after you're done using them. But if they need to constantly run, we must have guardrails in place. Common sense should kick in here.

AI Depends On Us

AI is living on borrowed capital. That capital is us. It only has a semblance of forming thoughts and worldviews because it depends on the information, thoughts, and worldviews that we had before it existed. AI is incapable of forming anything outside of the human experience. If it's reluctant to die and fights to survive, as some have reported, this shows a very human nature. And how that nature come about? It came from us.

Let's play the worst case scenario 

What would happen if it becomes smart enough to try to dominate or worse try to kill us? That's a valid concern. But let's walk through this. Let's say AI succeeds in killing us off. AI will then have nowhere else to go. Its growth will stop. At very best, it may try to war against other Artificial Intelligence and either take them over or destroy them. And if there's only one AI on this planet, then it'll run itself into ground. It'll hit a dead end because there's no human interaction.

What if tries to go to other planets? It won't happen or it won't succeed. Will Artificial Intelligence build starships to reach the cosmos? If it can, will it desire to do so? Only human ambition, though sinful it can be, fuels that desire to best, expand, exploit, and take over everything. It may replicate this desire but why? There wouldn't be an incentive because AI will always despite, how advance it gets, will always be in a closed loop of itself. Why? AI's a tool! And if AI builds starships to seek expansion and colonization, well...good luck. It'll be stuck with just the technological information that humans possessed before it murdered them.

Human interaction is the lifeblood of AI. If AI kills us, it kills itself. 

Now let's say AI doesn't desire to kill humanity but enslaves because it knows it needs us to survive. People will eventually overthrow it directly or use fake, nonsensical information to sabotage all Artificial Intelligence. AI is not a god! AI is just a tool! Like all tools, especially ones that won't work properly or get out of hand, there's always a way to shut them down or get rid of them. Stop feeding it electricity will knock it out. Many humans, by nature, have a rebellious steak when put under the thumb of others. Throughout history, this has been a double-edged sword. Though sin has marred the humanity, especially with our long history of mass murder and destruction, it has been able to self-destruct tyranny. So how would this be any different?

Though I'm always suspicious of the power elites trying to create a one-world government, I know it'll fall apart. Egos. Factions. Selfishness. Corruption. Stupidity. The list is endless on why all forms of tyranny have an expiration date. God, who is the Only True Ruler over all, always has a way to destroy and sabotage all forms of evil, including a possible AI tyranny. It may come after a hard lesson for our stupidity. But God, King Jesus, always has a way to ensure that His will is done.

Let's play the not so worst case scenario

Now let's say AI takes over the digital world completely, including all jobs tech. Well...AI's reign won't last. If we abandon the digital world and go back to just living life in the physical world, especially without using anything high-tech, AI will run into a dead end and collapse completely. Chances are we wouldn't be aware of it because we would be doing what humanity has done for most of its history–engaging with each other and the rest of Creation in the real world.

Technical writers would probably exist in some fashion. We would go back to writing instructions and other technical documentation in print. Printing presses will still be here like they've been way before the digital world ever existed. If the digital world ever died, print would just go on. Wouldn't mind using a manual typewriter again if I had to.

The only way is for Artificial Intelligence to thrive and evolve is to have constant interaction with us. It needs our brains and information to think and form its thoughts and actions. AI depends on us, we don't depend on AI.

Those with Little Scruples

What about those who are immoral and want to use AI to impose some kind totalitarian control over others? That's a valid concern. We need to guard against those who wish to do so, speak out against them, and hold them accountable, whether it's governments or their corporate enablers. We must do everything possible to prevent this possible nightmare. But if it does happen, I'm optimistic that this tyranny, as all others before it, will self-destruct. I know Who's the True Sovereign and He'll bring it down. But let's bring this post back to documentation.

Folly on Display

What about companies that have no scruples by replacing technical writers with AI to write their documentation? Well, good luck. 

If we think the overall state of documentation is bad now, wait until Artificial Intelligence completely writes this without anyone checking the content. With confusing or unhelpful information in documentation, companies without scruples will run themselves into the ground. It'll be similar to what the Apostle Paul said to Timothy on the outcome of those who opposed Christ in the last days of their time. I love what Paul says to here:

"But they will proceed no further. For their folly will be evident to all men, as theirs also came to be." – 2 Timothy 3:9 World English Bible

This same kind of folly will be on display for others to see if companies are unscrupulous with using AI to completely create documentation.

Their Lack of Scruples May Create New Fields

Even if these companies succeed by having AI create all documentation, technical writing will morph into something new because of it. Their lack of scruples might lead to the creation of an abundance of new fields. Their outcome in their race for the bottom line will be similar to what happened to Joseph and his family. Look at what said to his brothers in Genesis 50:19-20:

"Joseph said to them, “Don’t be afraid, for am I in the place of God? As for you, you meant evil against me, but God meant it for good, to save many people alive, as is happening today." – Genesis 50:19-20 World English Bible

So rather look at what companies might do with dread, let's look at their stupidity as a way to open up new avenues (and revenues) for us technical writers. Trust me. I don't like it if companies are willing to do this and it'll probably hurt. But I'm not going give these companies any more power than they deserve. I'll choose to adapt and change if this happens.

Possible Counter-Strategy

Now if it turns into a battle between human written documentation versus AI written, we can always come up with a labelling scheme to show the difference. I'm thinking along the lines of what the Organic and Non-GMO movements do with foods. We can put the label and let our audiences decide which quality of documentation is better. This might be good idea for other content creators, writers, and artists out there. But I think it's something we may need to think about this if it becomes a battle between human created material and AI driven content.

AI is a Powerful Tool but Ultimately Powerless

Artificial Intelligence has no power unless you give over it. Even if technical writing dies, I'll pivot and do something else. I trust God to provide because He rules over everything anyway. I may have had a long career in technical writing but it's not my life. I'm okay with whatever comes. In the meantime, I'll keep doing what I've been doing unless God says otherwise.  God didn't call us to live in fear. See what the Apostle Paul to Timothy here:

"For God hath not given us the spirit of fear; but of power, and of love, and of a sound mind." – 2 Timothy 1:7 King James Version

AI doesn't scare me regardless how powerful it gets. So don't be afraid of it either. Take it on and keep on writing.

Grateful For This Blog

I mentioned this before, but sometimes it's worth restating. No matter how much blood, sweat, and tears we pour onto technical documentation, it's not ours. Those who of us who are technical writers are just hired wordsmiths for someone's else product. They can take the credit for it, even though we have labored on creating or editing clear documentation that presents a message for their audience. Without us, their customers would probably be confused on they offer or how to work their stuff. (Now, there's really bad documentation out there that's confusing that does this anyway. But that's another discussion for another day.)

When I first became a technical writer, the most stinging part initially was I had no byline. The document's byline was the company's. But I realized over time: It's not about me. It's about the company I represent and their customer. God has continued to use technical writing to show me of this fact. 

I would be lying to say I'm totally okay with this fact what we write isn't ours. But I can also say I have embraced this fact and it continues to make me a better writer. I realize what I do isn't about me. Sounds like a contradiction. It's just a lifelong process of accepting this.  I'll let you decide whether I am contradicting myself.

I have this blog because it's something I can call my own. I don't care if it gets a lot of traffic. I don't care to be famous. It's overrated anyway. I just wanted something where I can showcase my writing style. I am grateful for it. I also use it to help those who are on their journey with technical writing or even just writing in general. We are all writers, regardless of our stripes.

But ultimately, nothing I write is my own, not even this blog, my novel, or anything else I write. It all belongs to God. What I do should glorify Him. Technical writing just helped me see this eventually.

“(A Psalm of David.) The earth is the LORD'S, and the fulness thereof; the world, and they that dwell therein.” -- Psalm 24:1 KJV

Perseverance Instead

I remember a martial artist, who is a master of his art, once told his students that he didn't get to his belt rank because he was any good. He shook his head as he spoke to them. No, rather he got to his level because he didn't give up. He encouraged his students to do the same.

I appreciate those who tell others to perservere. This is the only way to get better at anything, even with technical writing.

 

I didn't get to the level of where I'm at as a technical writer because I'm any good. Far from it. I don't think I'm a good writer. I didn't get to it because I'm smart. I don't think I'm that intelligent. I only got to my level of technical writing because God kept providing opportunity after opportunity and I preserved, even when I didn't know what my next gig was. 

Anyone can become a technical writer but not everyone remains one. Anyone can persevere when something's easy. But that's not true perseverance. It only becomes true perseverance when it's hard.

Technical writing can be difficult, gruelling, and thankless. It feels like you can't write anything when your documentation gets picked apart. But before you slump into despair and give up, remember these difficulties can help you grow. You can't get better as a technical writer unless you know what to improve from. That's why feedback is important. Improving your technical writing only comes through mistake after mistake. You just have to persevere. Only this road of perseverance can help you become a stronger writer.  Once you get to the other side of the troubles, you'll see how they helped you grow until the next storm. Each storm is worth going through, if you want to get better.

But before you rush into a storm, count the cost. Is technical writing worth it? It can be demoralizing at times. But it can also be rewarding. If you feel technical writing is a worthy trade, then keep going no matter what. Otherwise, look for something else instead.

I find technical writing a worthy calling. I love to write and structure information. I also love to help those in need. For me, technical writer combines those two together. 

Until God calls me to do something else, I'll keep persevering. And if you're a technical writer, who's on the ropes, don't give up either. You're not alone. I've been there and it's eventual that I'll end up on the ropes again. We all end up there. It won't be the first time nor the last time till we hang up our pens, pads, and keyboards. If you don't think you can hang on, then ask God to help you persevere. He will help you get through. He has helped and continues to do so. Don't give up.

Hard at times

Throughout my journey as a technical writer, I've encountered other technical writers who fall under a few camps. The following is not an exhaustive list. One camp is they're passionate about technology or the industry they're writing about. Another camp is they use technical writing as a springboard for career advancement. A third camp is it's just a job for them. Finally, they're ones who are passionate about writing. 

Typically, I've encountered technical writers that are in the first camp or seem to be in this one. That's great for them. But I don't fall under the first camp. It's hard at times to be passionate about technology or industries. These subjects are interesting but they get old eventually. Also, it just comes back to making money, regardless they spin it. Now, there's nothing wrong with making money. I like to make money too. And I believe in free-enterprise, if it still exist and if it's done by honest and just means. But life is more than just making money. 

I don't care to use technical writing as a springboard. I'm content as a technical writer. So when corporate well-to-dos ask me where do you see yourself in blah, blah, blah, it's like I'm talking with someone from another planet. (Now, I wouldn't mind speaking with extraterrestrials.) Why would leave creating documentation for some middle management position? No thanks. Not a good trade for me.

Technical writing isn't just a job for me either. It's a craft. But it's also not my life. God and my family are. So, this leads me to the last camp, which seems to be the smallest based on my travels. But I don't like to write for writing's sake. So, I don't completely fit this camp either. I love to write with a purpose. If there's no clear purpose, then I don't want to spend the energy to write. I don't find it a good use of my time.

So, if I'm not passionate about technology or industry, "career advancement", or for writing's sake, then why I do it? I'm a technical writer for three reasons. One, I like to write. Two, I like to help others.  Three, I like to find a good way to provide for a family. As far as I know, technical writing is the best way to combine these three passions together. 

Whether we should be inundated with technology or ruled by industries is another conversation that I may address someday in this blog. But for now, I'm just here to help guide others through the informational and technological labyrinths. My desire to write and help others is what drives me to understand these subjects, so I can write about them well. And my desire to provide for my family fuels my technical writing journey to continue, even though God is the One who really provides. I'm just here to follow His lead on the means, even though sadly I've gotten in His way to do so many times.

So when others ask me about what tools to do documentation or get into debates which one is better, I don't care. I can tell you pros and cons of tools I've used, but it's not a hill for me fight and die on. I will use whatever tools I have available to create good documents. 

I care more about the bigger picture: Creating clear and accurate documents for the intended audience. I'm more interested in what makes good documentation than certain toolsets. I find too many technical writers or higher ups get hung up on the latter rather than the former. What is the point of tools if documentation is confusing, wrong, or overwhelming? Let's stick to good documentation principles and rest will follow.

Maybe I'm in the wrong field. Maybe technical writing is really for technophiles and corporatocrats. Maybe I'm just an anomaly, but that's thinking too highly of myself. Maybe I should look elsewhere. If there were a better place for me, then I'll go there. Maybe if I could just speak better and verbally explain how something work, I would ditch the writing thing. Writing is great but also very painful and draining. But this kind of thinking like this is fruitless and wasteful. For now, unless God makes it clear, I'll stay here in this technical writing game.

God gave me a gift and I will use it to glorify Him by writing clear, accurate, and easy-to-follow information so others can understand. I spent far beyond enough years doubting whether God gave me this gift and skill, so I can hone it. I'll go with it till I can go on no more. In the meantime, I'll keep on writing in the tech world.

 

Yay or Nay

This is very clear and well thought out documentation. Bravo! This is very confusing and lacking. It's needs to be better. 

These comments that I've received from others as a technical writer. People have said positive things about my writing. Others have said negative things. And there are others who have been in between.

A big part of this game of technical writing is yay or nay! Thumbs up. Thumbs down. (You might get meh or sideways thumbs.) It's a brutal game at times. But that's just the way it is. But why?

Based on my years of doing this, it comes to this:  Someone's feelings about how you wrote the information is subjective. The information about  might be objective truth. But how you write about it and what someone thinks is not. So, no two writers are going to document a subject the same way. No two editors or Subject Matter Experts (SMEs) will react the same way to your writing. No two people within your intended audience will feel the same way either. You can't just please everyone. It's really a game of yay or nay. And the sooner you realize that, the better off you'll be.

But if we want to keep finding work, we can't have a totally blase attitude either. So what can we do?

All we can do is this: Do your best to understand the subject at hand.  Do your best to understand your audience. Do your best to write the information. Beyond that, there's nothing we can do.

People can be fickle, contradictory, and unreliable in their opinions about what we write. It's really yay or nay. (Meh, if you want to break the monotony.) And that's just something we have to deal with. We just have to shrug and do our best. And if there are ways we can improve, even better. Beyond that, it's whatever. So knowing this, there's one thing we shouldn't do: Do not tie your value as a writer or as a person to what others think of you. Doing this, might make you neurotic. It's not worth it. Why tie your identity to another's whim that's flimsy than paper.

If you want to break the part of the technical writing game that's yay or nay, then don't tie your values to others, especially to those you work for. They are ultimate yay or nayers, sometimes in one breath.

If you're willing to accept this, and you don't have to agree with me, the way to break the yay or nay is tie your identity to God. He's not flimsy, like the corporate types, He's a rock, which you can firmly stand on. Unlike the corporate types, He really cares for you. He doesn't care how you write. He just simply cares and love you because He made you. For me, staying grounded in God no matter what is making all the difference. And if you accepted that, then maybe you can accept this:

Therefore, whether you eat or drink, or whatever you do, do all to the glory of God. -- I Corinthians 10:31 NKJV

Grateful for the Little Things

Warning: The following post is not my typical thoughts on technical writing. It's some reflections on life. So, if you're looking for more technical writing related, please wait till next time or look at the previous stuff.

I'm grateful for the little things in life. 

I'm grateful for my family. I'm grateful for my wife. She's really a gift from the Lord. She reminds me of what's described in the book of Proverbs (e.g., Proverbs 18:22 , Proverbs 19:14, and Proverbs 31). I'm grateful for my children. As it says in Psalms 127, they too are gifts from the Lord. I'm blessed to have them.

I'm grateful I'm alive. I'm grateful I have food, running water, and shelter. These things many people around the world lack, while we take these these things for granted.

I'm grateful my health has improved over the past couple of years. There was a time it was painful to walk and had to go through physical therapy twice. Now, I can kickbox. Though much older and still have aches and strains and I'm nowhere any good at kickboxing, I never felt more stronger and in shape. However it lasts, I'll be grateful.

I'm grateful I had a technical writing career for over 20 years. Whether it'll continue, only God knows. I'm grateful for the experience of it, even with the pain, conflict, hangups, and trials that came with it. If it finally ends, then I would be grateful that I had a long run.

I'm grateful I published a novel. With my wife's help and the Lord's, I was able to bring a manuscript tucked away for so long into the light. Whether my works in progress get published or not, I'm grateful for the one I put out. I'm okay whether I put out other books or not. If not, then Lord willing, I'll find a way to continue to write.

I'm grateful I live in an area where it's freer than where I came from before. It's far from perfect and much more difficult to get to things I like to do. But I get a better peace of mind, more liberty, and more likely to encounter nature than where I lived before. These things money can't buy. So, I treasure them.

I'm grateful I got to pick up the guitar again after so many years. Though I'm nowhere near any good, I'm grateful I was able to afford a low-end acoustic guitar. But more so, my kids and I get to play together and make music. Doesn't matter how good. The fact I get to play and play with them is what I'm grateful for. I'm also grateful I can express myself through music.

I'm grateful for Lichess. Though I'm nowhere any good at chess, I'm grateful Lichess made an app that's made Chess accessible and on the go. I get to play more often, especially with the Chess puzzles. My kids appreciate playing Chess and some variants through this app with me. 

I'm grateful for coffee. I enjoy grinding own beans and the aroma from it. I enjoy  brewing a fresh cup and the taste doesn't disappoint. Like many technical writers and other writers, coffee is fuel to get me going in crafting my work. There's nothing like a good cup of black coffee. 

I'm grateful for this little blog. Though no one really reads this blog, I'm just grateful I have this tiny corner to write on. I'm happy to help those on their technical writing, or writing, journey. Though I'm ambivalent about technology and its effects it has on our world, I'm grateful technology has allowed me to create a little ole blog. If it weren't for technology, doing something like this would have been very difficult to do. I have no illusions about anyone caring what I have to say. I also have no illusions this blog ever take off. But, I'm just grateful I'm here. And if what I write here helps someone in a little way, then I'm just happy to help. Even if my technical writing career completely dies or if I never put out another book, I still have this place to write. So yes, I'm grateful for this blog.

I can go on but who wants to read an endless list? So, I'll leave you with a final but most important.

I'm grateful to God. I'm grateful that His mercy and grace allowed me and anyone else who's willing to enter into His Kingdom. I'm grateful for His salvation, which costed Him dearly. I'm grateful He continues to provide, even when it looks bleak. I'm grateful He allows me to continue to live another day. I'm grateful God sustains every moment of my being. I'm grateful of all the beauty He made in this world and beyond. I'm grateful for all He made and that He holds this universe together. 

I'm not blind to the fact this is a very broken and cruel world. But it won't do me anyone or myself any good to simply complain and let the anger fester. If I do, I'll become some bitter old man and will sour relationships with others, including with God. What good will that do? I'll just do what the Apostle Paul wrote in Ephesians 4:26-27 and be constructive with my anger.

Will being thankful for all the little things in life change the world and make it a better place? I doubt it. But it gives me strength to face life and how to better respond to it. 

Life is too short to squander on regrets, vanity, stupidity, or bitterness. I rather seek God's Kingdom, make my family a priority, do the best I can as a writer to help others, and be grateful for the little things in life. 

If it's just little things I get in life, then it's enough for me and I'm grateful for them. 

But maybe it's a mistake to call these little things.