For people who know me or who have been following the blog for a while… you know my professional background is in Technical Writing and Illustration. I also have been a forum moderator at the DBSTalk Web site for many years now. As part of some recent logo redesign for that Web site I wanted to recreate the previous logo design as closely as I could to have a baseline for comparison purposes. I needed to do this because the original high-resolution source was lost and I did not create that previous design.
Long-story short, the previous Web site logo design for DBSTalk used a Dish Network Direct Broadcast Satellite (DBS) dish as a cornerstone around which the rest of the logo was created. Before working on any actual logo work, I first created this vector illustration of a Dish Network 1000.4 DBS rooftop dish assembly.
Even though I didn’t end up using this in the new logo redesign, I was pretty proud at how this turned out. I may even upgrade the satellite dish on the ‘Sects cave-teepee at some point just to see if anyone notices! 🙂
Please let me know what you think and remember, if you are interested in requesting my services as a Technical Illustrator, please use the Contact page and provide me with as much information as you can about your request.
When I was a Technical Writer/Illustrator at ON Technology, I needed a clean vector version of the corporate logo for various print and online projects, so I drew one:
I had a friend there who obtained certification as a Certified Novell Engineer, and he wanted an official version of the logo to include on his resume and business card so I dew him a clean vector version of the official logo:
Working as a Technical Writer at ABB, Power T&D I needed a clean resizable version of the ABB corporate logo but could not find one. Since I was redesigning the documentation templates to meet corporate standards, I also researched the corporate logo and created a vector version of it to corporate specifications:
For many writers, whether creative or technical, a visit to the Editor seems like a visit to the Principal’s office. It’s easy to see the Editor as someone who tells you how wrong you are or who tries to restrain your creativity. The truth is that a good Editor helps you achieve your vision if you will allow it.
If you are a Technical Writer working for a company, the Editor has many responsibilities. The easy part of an Editor’s job is to enforce corporate standards as well as use of proper grammar and spelling. I say easy not to dismiss the work involved, but because a good Editor will be well-versed in these things and able to suggest corrections fairly quickly. You do not define these rules, but you must work within them, and the Editor is there to assure you do so.
An often overlooked job of the Editor, however, is that of ensuring the writer’s message comes through. The names and actual subject matter are omitted to protect the innocent… but here’s an example of a situation that demonstrates how much an Editor adds to a completed work.
The general process at a place where I worked as a Technical Writer was to complete a couple of drafts of a user’s guide and when it was considered technically accurate, schedule an Editor review before sending the document out for a final review and approval for publication. This meant the Editor was usually seeing a document that I believed was complete, accurate, and hopefully without errors. If I had done my job correctly, I should see few suggestions for change from the Editor.
As an aside, I find working in corporate environments there seem to generally be three categories of Technical Writers in terms of how they apply Editor feedback: 1. Writers who make all suggested corrections without question, 2. Writers who choose to ignore some suggested corrections without discussion, 3. Writers who discuss the feedback with the Editor to be sure they are both on the same page. I consider myself to be the third type.
On one particular occasion, my Editor had considerably marked up a particular procedure for installing a piece of hardware. I read through my original writing and her markup several times and came to the conclusion that I did not know what to do. To put it simply, her suggestions were completely incorrect and were not at all possible given the hardware as I knew it.
So I approached her and explained the situation just as I have here, and I added that while her suggestions were incorrect it was also clear to me that what I wrote was also incorrect. That she could read what I wrote and think what she did was a strong indication that what I had intended to convey was not getting through. I explained to my Editor what I was attempting to convey to the user, and then understanding what I had originally meant, she was better able to help me write what I needed.
I could have ignored her feedback and been wrong… or accepted her initial feedback blindly and also been wrong… but embracing the process and the point of having an Editor made for a stronger procedure in a better document. This is why you need an Editor.
In creative writing, unlike Technical Writing, you get to make more of the rules and can choose an Editor more tuned to the style you intend to write. Everything else I said above still applies, however. Interacting intelligently with your Editor will not just make your writing look good, but it will ensure the story you are intending to create is the one your readers will see when they read your book.
So, don’t view the Editor as some form of punishment. Your Editor is there to ensure you do the best work you are capable of producing. Interact with your Editor as much as possible with regards to feedback so that you both are on the same page. Your readers will thank you for it and you, in turn, should thank your Editor.