Why it's so hard to do this blog post

So, I've got most of the next tutorial written out, and I'm trying to find some time to get it done.  It happens that I've got an interview with a particular company out in Seattle next week, and I've been putting together travel plans, getting extra stuff done at work and cramming on some C# knowledge to prepare.  I'm definitely going to try to get the post up by this weekend, but no promises.

I'm looking into new ways to do it as well.  Right now, I write out the program (which is just adding on to what we have so that it's a continual building process) then I go back and start writing the post.  The reason this is inefficient is because I'm trying to remember the order I wrote the code in, the going back and swapping things around to make better logical sense, and then trying to make sure that I remember to include everything.  The actual writing, once I get this prepared, is more stream-of-consciousness, which is tricky because I'll ramble and have to go back to try to make things more concise and clear.  It's no good to anyone if the reader (you), doesn't understand what I'm talking about.  One of the first programming books I ever bought assumed a fair knowledge of programming standards, and therefore, the book was practically useless to me, because I only had a passing knowledge of BASIC at the time.  I remind myself often that I want this to be accessible to anyone, from the complete beginner to those guys at Microsoft that keep popping up on my WebStats page.

In other news, if you are a sim fan, Silent Hunter IV is coming out in the next day or two.  I'm a big fan of the series and I'm really looking forward to it.  There's always some issues to work out, but the mod community is ever diligent in making the game more and more realistic.  Which pretty much just means that I sink more often, but it's still fun.

So, hopefully another tutorial post this week, and a full recap from my trip out west when I get back.

-Brian