(no subject)
Jul. 21st, 2009 11:14 amShared pain is lessened -- but shared proofreading is less effective.
My counterpart in our other facility and I were both asked to proofread the company's new website. She called me this morning to split the task, so we don't do redundant work. We began to discuss sections we'd already started to cover, and issues we had unearthed. In about 10 minutes, we discovered that we had both read the Software section -- and I had noticed a bunch of typos and one spectacular bad link, and she had found a lot of mismarked trademark issues, missing graphics, and some other stuff.
With a deep sigh on both sides, we've concluded that the company will be best served if both of us proof the entire thing, since we are catching different problems.
My counterpart in our other facility and I were both asked to proofread the company's new website. She called me this morning to split the task, so we don't do redundant work. We began to discuss sections we'd already started to cover, and issues we had unearthed. In about 10 minutes, we discovered that we had both read the Software section -- and I had noticed a bunch of typos and one spectacular bad link, and she had found a lot of mismarked trademark issues, missing graphics, and some other stuff.
With a deep sigh on both sides, we've concluded that the company will be best served if both of us proof the entire thing, since we are catching different problems.