| |
Ten Quick Tips for Inexperienced Writers
By V. Berba Velasco Jr., Ph.D.
One of the biggest problems that inexperienced writers have is simply knowing how to get started. If you've unsure of your writing skills, then here are some quick tips to help you get started.
1. Get yourself a thesaurus—or better yet, two of them. These can be tremendously helpful tools when you're struggling to find the right word. A thesaurus is no substitute for a solid vocabulary, but it is still helpful in a pinch.
2. Avoid using the same word too frequently. This can make one's work sound repetitive. Again, a good thesaurus can be helpful in this regard.
3. Keep your sentences fairly short, since longer sentences can sound unwieldy. I've found that 17 words or fewer is a good guideline. Do remember that this is just a guideline, though.
4. Even as you keep the sentences short, make sure that they flow together well. Sometimes, unskilled writers will simply chop longer sentences up into shorter segments that don't blend together smoothly. If in doubt, try rephrasing the sentences or adding the proper connective phrases (e.g. “then,” “so,” “as a result”).
5. Get a copy of “The Elements of Style” by Strunk and White. It's a short book, but incredibly helpful. There is no better reference for aspiring writers.
6. Don't rely too much on your word processor's grammar checking features. They can be quite impressive, but their capabilities are still quite limited. Spelling checkers are also limited in their capabilities, since they cannot recognize a lot of proper names and technical terms. In addition, spell checkers cannot detect situations wherein the user has entered the wrong word in place of the proper one.
7. Proofread, proofread and proofread… over and over. When you're done, have a friend proofread your work as well.
8. Remember your target audience. Ask yourself, “What information will my audience require in order to understand what I'm saying?”
9. Avoid clever wordplay unless you're sure that it will work. In most cases, it is best to gain more writing experience before trying something witty.
10. Remember the artists adage, “Practice, practice, practice”? If you want to become good at writing, then write, write and write!
About the Author
V. Berba Velasco Jr., Ph.D. is a senior electrical and software engineer at Cellular Technology Ltd (www.immunospot.com, www.elispot-analyzers.de, www.elispot.cn), where he also has various technical writing duties.
Article Source: http://www.simplysearch4it.com/article/779.html
| If you wish to add the above article to your website or newsletters then please include the "Article Source: http://www.simplysearch4it.com/article/779.html" as shown above and make it hyperlinked. |
| Some other articles by V. Berba Velasco Jr., Ph.D. | Using 'Get' and 'Set' Might Be Something You'll Regret
It's an all-too-common pitfall. Programmers who attempt to write object-oriented code decide to make all of their data variables ...
People Who Think They're Right
A few months ago, I had a conversation with a churchgoer who complained about religious intolerance. He said (and I paraphrase), "When it comes to religious beliefs, ...
A Common Misconception about Object-Oriented Programming
I've seen it time and again. A computer programmer proudly proclaims, "Yeah, my code is object-oriented. See? My data members are all private, and they can only be reached through public member functions. That's ...
Listening Techniques For More Effective Meetings, Part II
In Part I of this article, we discussed the importance of active listening, and how it is important for smooth and effective meetings. In the process, we touched on the topic of ...
Listening Techniques For More Effective Meetings, Part I
We all know what it’s like when a meeting doesn’t go smoothly. Discussions get derailed, tempers start to fray, and things are seldom resolved to everyone’s satisfaction. In such ...
Don't Forget the Internal Software Documentation
Internal documentation. It's one of the most frequent casualties in software development.
It's not hard to see why. For most companies, time ...
|
|
| |
|
