amenjonathan (10/1/2010)
Personal rant about blogging is how long it takes. I'm already reading SQL mags and studying for a cert, and all this after putting in 40+ hours per week. The blog posts I've written tend to take at least 2 hours to write, because I do a lot of research to link to sources and images. I wish there was a faster way somehow, although I'm pretty sure there isn't!I've been thinking about blogging just once per week. I guess that would be doable.
Document what you do at work.
Take that document and generalize it - removing company specific information from it.
Use that for your publications.
Work once, rewarded twice is my motto!
I was on a consulting gig once and developed some general purpose techniques and code to help them solve a problem. I went to the client's manager and said, "I can show your staff how to use these utilities, but they won't have to deal with them for another 6 months or more, and they'll most likely forget by then. Would you like me to document them for you?"
I'll never forget the response he gave me, "You would do that for us?" He was utterly amazed at the idea of a developer documenting something.
I'm thinking to myself, "Hey, not only am getting paid to write this up to provide top notch service, but I know a publication that will pay me $250 a page for it."
Boy, did my woodshop get a lot of new tools that summer. :w00t: