This is a good base. I don't post screenshots or scripts from work. I do modify anything scripted to be generic (note, I have occasionally messed up but fortunatly work naming standards are generic).
I started mine as an experiment, then it became a notepad for myself and when I found stuff to write it up and send to my friends. Later it became part of my stuff for Drupal and now it's back to my big notepad mainly PowerShell but it's going to start moving into SCOM. The stuff you write is in search engines and Internet archives. So definitly remember that. Taking stuff down has a limited effect. Some other random thoughts a. If your blog engine has the ability, set a time out on commenting. Comment spam generally tries for older unmonitored posts. It also cuts own on unwanted support requsts. My post comments lock after 2 weeks, but mine is also back to being a low traffic site as I don't post regularly. b. Find a name for yourself. Semi-generic if posible, your writing will shape your site more then your name and I certainly had no idea my present site would survive as long as it did. Domains are cheap and most blog sites have a way for you to use your own domain name. c. It is great when you search for a solution and get your own site. :) d. if you explain something to people more then twice, you have content for a blog post. Steven Peck http://www.blkmtn.org On Thu, Sep 20, 2012 at 6:09 PM, Ken Schaefer <k...@adopenstatic.com> wrote: > **a) **I wouldn’t use anything from your actual work environment. > Setup a lab if you want to post screenshots. Using work equipment has > myriad issues: legal ramifications for you is something goes wrong, or if > an attacker is able to use this information to get access to your > environment**** > > **b) **If this is going to be available to others, then write > professionally: what you write will be “out there” forever so to speak. At > least, with a blog, you can update/change the content if there’s an error. > But if write like a 12 year old teen, then people will draw inferences from > that. When you next go for a job or maybe get asked to contribute an > article to a magazine, speak somewhere etc, people will google you, and > your past efforts will come up J**** > > **c) **Be prepared to be flooded with spam, inane requests and all > sorts of things. I haven’t put anything on my blog for years, yet people > still think I’m a free IT resource. Most are polite, and get it if you > can’t help. Some are really weird and have some kind of entitlement > mentality.**** > > ** ** > > Good luck**** > > ** ** > > Cheers**** > > Ken**** > > ** ** > > *From:* Jon D [mailto:rekcahp...@gmail.com] > *Sent:* Friday, 21 September 2012 12:27 AM > > *To:* NT System Admin Issues > *Subject:* Personal IT Blog?**** > > ** ** > > I was kicking around the idea of starting a personal IT blog to keep track > of the things I work on.**** > > Seems like if nothing else it would be a nice feather in the cap when it > comes time to look for a new job.**** > > I'm curious if anyone else does this?**** > > **** > > If anyone does do it, anything to think about?**** > > Obviously any screenshots would need server names, IPs, etc blanked out.... > **** > > ** ** > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to listmana...@lyris.sunbeltsoftware.com > with the body: unsubscribe ntsysadmin > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
