When I started up this second attempt at a dev blog, I committed myself to at least on blog entry for every day of work for the first 90 days.  That has turned out to be harder then I thought.  By the numbers I’m ok, because I’ve been making entries on non-work days (usually as I’m playing with some other technology).  But the idea was actually a blog entry ON the actual work day, and by reckoning, I’m now 3 days behind.

The problem is that for the past few weeks my work day has been debug / old systems (vs2005) support.  And a lot of what I am doing is either tedious, VERY difficult to explain coherently without a 20 page treatise on the background of what I am doing, Old tech that isn’t interesting, or is too proprietary to my Clients to safely take about, or all those.  And also let’s face it after a day of intensive debugging the last thing I want to do is spend more time on the computer.  By the end of the day, I’m wiped out!

Finally I DON’T want this blog to become a “personal” blog site, if it isn’t directly related to my work, I’m not going to make an entry (the occasional Geek Movie / moment not withstanding).  This blog entry is, in itself, on the edge of what I think is acceptable for a professional blog.  So I’m going to try to stay with the 90 days goal, but I think it may not be the original intent of one blog entry per day. 

I’ll have at least 65 blog entries in the first 90 days to see if I can get myself in the habit, but I’m not going to set up a rule that may lead to failure.  Methodology must change for the circumstances or your methodology isn’t helping you in the long run.