• I know I'm very late to the conversation, but a few things...

    People learn in different ways. Just because there's an article out there describing RAID configurations doesn't mean Joe SysAdmin is going to get it because of that article. Your article, which may come at it in a slightly different direction or just your choice of words, or the fact that Joe SysAdmin is processing multiple articles may lead to Joe "getting it." So just because you see an article out there on something doesn't mean you have to stop from writing about it, too.

    You don't have to be an expert to write. One of my first articles on the old swynk.com garnered a reply from none other than Steve Jones who offered a different perspective on the same topic. It gave me a lot of things to think about and I went ahead and amended my article with some of Steve's points because they made a lot of sense. The majority of us aren't in the Kalen Delaney or Itzik Ben-Gan stratosphere of SQL Server knowledge. We don't have to be. Which is a good thing, or I'd have never written anything...

    Time is always an issue. It's why I bounce in and out of the forums and the blogs where I'm posting like a madman for a few days and then disappear for weeks at a time. I keep telling Steve I'm going to start writing again and then I get busy between work, family, and ministry. I do know that when I was writing all the time, it was easier to write (as Phil Factor indicated). I do a lot of writing now, but it's for ministry, and I know that's something I'm called to do. Here's the thing, when I was churning out SQL Server articles once or twice a month, I found writing about 15-20 minutes a day was enough to get that kind of output and more. Since I'm writing daily for ministry and since I'm doing a lot of checking, cross-referencing, researching, exegetical analysis, that kind of writing takes a lot longer. But the technical writing is finding a particular topic you have an interest in, spending probably 2-3 hours over the course of a week or two and it's out there. Which I guess incriminates me for not writing on here more. *shrug*

    K. Brian Kelley
    @kbriankelley