[null, {"document_url": "https://ascriptor.blogspot.com/2010/10/", "unformatted_src": "//4.bp.blogspot.com/-aBZ8kGAfeww/UHjlB8KQaPI/AAAAAAAABcg/l4LLIG_r3nI/s320/blueprintPaid.jpg", "src": "http://4.bp.blogspot.com/-aBZ8kGAfeww/UHjlB8KQaPI/AAAAAAAABcg/l4LLIG_r3nI/s320/blueprintPaid.jpg", "formatted_filename": "blueprintPaid", "rendered_width": 320, "rendered_height": 212}, null, {"document_url": "https://ascriptor.blogspot.com/2010/10/", "unformatted_src": "//3.bp.blogspot.com/_3t-9nSNtW00/TK1eBaHcfBI/AAAAAAAAAIw/efx86daQK2M/s1600/TTInitials.jpg", "src": "http://3.bp.blogspot.com/_3t-9nSNtW00/TK1eBaHcfBI/AAAAAAAAAIw/efx86daQK2M/s1600/TTInitials.jpg", "formatted_filename": "TTInitials"}, null, null, {"document_url": "https://ascriptor.blogspot.com/2010/10/", "unformatted_src": "//2.bp.blogspot.com/-BpJ95dU8QwA/UHjeljJio0I/AAAAAAAABcQ/NCVFd36y4CQ/s320/library.jpg", "src": "http://2.bp.blogspot.com/-BpJ95dU8QwA/UHjeljJio0I/AAAAAAAABcQ/NCVFd36y4CQ/s320/library.jpg", "formatted_filename": "library", "rendered_width": 212, "rendered_height": 320}, null, {"document_url": "https://ascriptor.blogspot.com/2010/10/", "unformatted_src": "//3.bp.blogspot.com/_3t-9nSNtW00/TKpNc2febZI/AAAAAAAAAIo/_ILBnfSQVSU/s1600/TTInitials.jpg", "src": "http://3.bp.blogspot.com/_3t-9nSNtW00/TKpNc2febZI/AAAAAAAAAIo/_ILBnfSQVSU/s1600/TTInitials.jpg", "formatted_filename": "TTInitials"}, null, null, null, null, null, null, null, null, null, null, null]
Wednesday, October 6, 2010

Software Development Life Cycle When I'm not coming up with story ideas, writing short stories, or working on my current novel - I'm usually working in the computer and wireless technologies industry.  A significant part of my work history has to do with programming and the development of software.  Some of this geeky influence can be seen in my fiction writing as well.
As a programmer and developer, I've always been a big advocate of the Software Development Life Cycle (SDLC).  It's a very fundamental aspect of designing applications.  Just as a house builder has to go through the proper planing steps and put together a blueprint for the desired product - a software developer needs to put forth a blueprint as well.

One of my claims to fame, or lack thereof, has been my paper/guidelines on the SDLC.  I wish I could count the amount of email and thanks I've received for this small contribution to the programming community.  The world of programming has been major blessing to me throughout my career in the computer industry and as a freelance writer.  I felt that if I could give anything back to the community, it would be through my brief, but handy, guide to the SDLC.

So, I've re-posted this paper as a page on this site.  Feel free to use and abuse it as much as you want.  If you have any comments or decide that this has helped you so much that you want to contribute to my financial life style, I'm always open for discussions. ;)  Now all I need is a Story Development Life Cycle guide. Posted by Unknown at 10:44 PM No comments: 
Monday, October 4, 2010

What and How to Read? Lots of Books

Today I visited one of my favorite book stores - Half Price Books.  Normally I check out the computer books, the software, videos, and the science fiction books.  This time I also took a look at the books on writing.  Wow!  So many books about how to write books.  I was overwhelmed.  I looked at many of the titles with the expectation that I would end up walking out with one or two in my arms.  However, after about a half hour of exploring, I came away empty handed.  Why?  Well, with all the great expertise, recommendations, and guidance on how to write the next great novel, I came away with the same conclusion that I have always had.  If you want to be a writer - read!  Nowhere else can you get a great education on how to be a writer than by reading books by other great writers.
Don't get me wrong!  I own some great books about writing:
All of these are great books to have sitting by my writing desk.  However, it still boils down to three things - reading, reading, and more reading.  Not just reading like you're out in the lounge chair with a cool glass of sweet tea off to side, which is okay for enjoyment.  But, read the structure of the story.  How does the author start the book?  What keeps you interested after you get past the intro?  How are the characters defined?  How is the dialog between the characters handled?  What about what the characters are thinking?  Are the sentences short and to the point, or complex?  How is the punctuation handled?  These are the things I start to examine when I want to know how to write.

Another thing to look for is the voice of the author.  Some are very detailed, like Tom Clancy.  He could spend an entire chapter on the details of how to listen for submarines.  Others give you just enough to let the imagination run wild.  I like how Orson Scott Card gets into the mind and feelings of his characters.

So, while my time at the book store was enjoyable, I guess it would have been better spent just reading.  Back to The Rock Rats!  (Thanks Ben.) (Library image courtesy of -Marcus- via FreeDigitalPhotos.net)
Posted by Unknown at 2:58 PM No comments: 

Site Menu Articles Archive