I’ve done this for eight years to the month. I’ve taken my passion for PowerShell and written about it. I desired to play a role between PowerShell and its concepts and you, the reader. I’ve written for myself in some ways, to better remember concepts and to create a collection of code I might come back to again. But I’ve done more than just that.

I’ve fallen in love with writing. Again maybe. While this isn’t my normal every week post, I’m going to take advantage of this little platform that I’ve created for myself, and share, not about PowerShell, but about my desire to write. Maybe you know someone, that knows someone, that knows someone. How I feel about PowerShell has been apparent; the writing is what’s changed me though. I said again, a moment ago for a reason.

See, I hated grammar and parts of speech in grade school. I’m all about it now, but you know what I did love then, though? My journalism classes. How I didn’t combine the two classes in my mind is kind of lost on me; I’ll blame it on my grade school age. Then again, even though I didn’t like it, I do remember learning some things. So, I took multiple, year-long Journalism classes. I scheduled interviews and asked people questions, and then wrote things down, and then wrote things up, and shared with our readers—my fellow school mates. Your quick investment in reading was hours of mine preparing it for you.

Here’s a weird one. Some of my favorite times at work is when I’m writing email. Huh? Right. I’ll combine four, five, or six sentences, in an attempt to clearly and accurately convey a topic, a concern, a question, or questions. A something. Whatever it is, it’s that mini accomplishment that I enjoy over some of the others during my day. It may be how you know you love to write; it’s turned into that for me. Sometimes I’ll read what I wrote again after hours, and determine how it could’ve been better written, or how I could have written it to be less confusing. It happens; writing is an iterative process, and no one wants to spend too much time on a simple email, or two. Sure, I guess.

Why am I writing about this? It’s because someday I want an employer to pay me to write, to do what I love. I want a specific thing to write about—a single, specific technology, as a profession. I want to be a technical writer—a content developer. I want to play the middleman between technology and the people that need, or want it, or have to have it even if they don’t want it. The irritated needful: the best and worse audience. I want to supply the reader so well that they’ll know I value their time more than my own.

The easier something is to understand, the more grateful those that are forced to learn about it may become. I want to break down the complex; I want to begin with the simplest example from which we could start. You know, what I’ve done right here for years now. Making the complex, complex, is easy. It comes that way. Making the complex, easy, is what each of us hopes for when there’s a requirement to learn something new. At least to begin.

If you got this far, then let me know if you have any ideas for me. I have years of technical experience, but now, I just want to make someone’s customers pleased they read what I wrote. Without customers, forced—because they have to, or earned—because they want to, there’s nothing. Whether they must use you, or not, give them what they need without them having to ask for it first.