The Artima Developer Community
Sponsored Link

.NET Buzz Forum
Thoughts on Writing

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
Randy Holloway

Posts: 443
Nickname: randyh
Registered: Aug, 2003

Randy Holloway is a developer and writer focused on enterprise software.
Thoughts on Writing Posted: Jun 19, 2004 9:52 PM
Reply to this message Reply

This post originated from an RSS feed registered with .NET Buzz by Randy Holloway.
Original Post: Thoughts on Writing
Feed Title: Randy Holloway's Weblog
Feed URL: /msdnerror.htm?aspxerrorpath=/rholloway/rss.aspx
Feed Description: Commentary on Yukon, the CLR, and related technologies interspersed with personal opinion.
Latest .NET Buzz Posts
Latest .NET Buzz Posts by Randy Holloway
Latest Posts From Randy Holloway's Weblog

Advertisement

Fritz shared his thoughts on writing a while back (I just saw this today though), so I thought I'd post my perspective as well.

My biggest problem with writing is that I can often write extensively on a subject, even while I'm still in the stages of learning and synthesizing information. The impact of this is that I've found myself in the situation of cranking out written works to meet deadlines that really could have used more cycles for the inclusion of better information and more insight on the technology. This is especially a problem when working with periodicals, because the deadlines are tight since most magazines have to be published monthly. I've written one or two articles in the past that definitely could have used another week or two of work. When they were published, I looked back and thought "I'm not happy with how this turned out." So when I started my book on SQL Server 2005, I told myself I would not allow the deadlines to drive me to that kind of behavior. So far, so good. However, I'm still struggling with the process of writing on a new subject that people are still learning about. I'm still learning about the product, elements of the product have changed as I've been writing over the past year, and that process will continue through the end of this year. It is an interesting process, yet it feels risky from an intellectual standpoint. I've tried not to rush the process, but even so I'm still learning as I write. It can cause you to doubt your work.

One thing that I've found that helps me to gauge my own level of understanding on a technical subject (or any subject for that matter) is to give a talk or lead a group discussion on the topic with a specific agenda. I find that if I can talk about the subject comfortably and present the material to a small audience before writing about it that I can easily gauge my level of understanding and comfort with the topic. I've given a couple of talks in the past where the material was still too fresh and I didn't have the command of it that I wanted to have, and that can be a terribly disappointing experience. You don't forget it quickly. However, by going through that kind of exercise I can also make sure that something that I need to write can be verbalized in a clear, concise, and appropriately descriptive and informative manner.

Read: Thoughts on Writing

Topic: Web Setup MSI fail when used on Servers with the Loopback Adapter installed Previous Topic   Next Topic Topic: Why You Should Dump Internet Explorer

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use