TaoAnomaly - Slashdot User

Comment A DMS is the only way to fly. (Score 1) 401

by TaoAnomaly on Friday February 20, 2009 @02:22AM (#26925951) Attached to: How Do You Document Technical Procedures?

Getting the procedures out of peoples heads is a huge money saver for the business down the track. Check out www.businessfitness.net. While we mainly deal with accounting firms out software can be used for any business and has a number of features to help facilitate better procedures. We provide basic templates for procedures, checklists, letters etc and this system has been specifically built for Document and Record Management. Hope this helps. Either way when writing procedures ensure that someone else reads them that does the same function or even better get someone to follow your procedure while you do the function and if you miss a step they can pull you up and get it added to the procedure.

Comment A DMS is the only way to fly (Score 1) 1

by TaoAnomaly on Friday February 20, 2009 @01:50AM (#26925809) Attached to: How do you document technical procedures?

Getting the procedures out of peoples heads is a huge money saver for the business down the track. Check out www.businessfitness.net. While we mainly deal with accounting firms out software can be used for any business and has a number of features to help facilitate better procedures. We provide basic templates for procedures, checklists, letters etc and this system has been specifically built for Document and Record Management. Hope this helps. Either way when writing procedures ensure that someone else reads them that does the same function or even better get someone to follow your procedure while you do the function and if you miss a step they can pull you up and get it added to the procedure.

Comment Re:bad (Score 5, Informative) 401

by ChadDa3mon on Thursday February 19, 2009 @12:58PM (#26918273) Attached to: How Do You Document Technical Procedures?

I think you misunderstood what I'm saying. I'm not documenting this for 'my' job, nor am I worried about my job security. I am trying to write documentation for 150 people around the world to follow so that we're all doing things the same way.

Submission + - How do you document technical procedures? 1

Submitted by ChadDa3mon on Thursday February 19, 2009 @12:11PM

ChadDa3mon writes: I work for a large MSSP type operation and we deal with a plethora of vendors, versions, and....skill sets. We're facing a critical problem as we grow when trying to deal with these varying degrees of technical competency. The end result is we're getting to the point where we have to document every procedure and process, no matter how mundane or 'common sense' it may seem.

I've got a picture of how I'd like this to work in my head, but I can't find any software out there that seems to go along with it. I'm a big fan of keeping things simple, so I'd like to start with high level overviews. Each step in the process would be a general statement like "Look for valid traffic on the monitoring interface". For those who already know what 'valid traffic' means, it's easy to follow. However, if there was someone who was unsure what it meant, there would be a link they could click on that would pop open a new window (or something similar) explaining in detail what we're looking for and how to find it. It's my hope that using this process, people aren't just blindly running commands, but gaining an understanding into what that command is, and why we use it, what to be aware of etc....

This seems like a job for a flow chart, but I don't like the setup of any of the ones I've used, such as Visio. It could also maybe fulfilled by a wiki, but there's so many out there I don't know where to start. I have to assume I'm not the only person who's facing a problem like this, so I'm hoping someone else out there can make some recommendations.

Comment Re:Not at all... (Score 1) 348

by ChadDa3mon on Thursday May 01, 2003 @07:15AM (#5851322) Attached to: OpenBSD 3.3 Released

MS Windows NT family (ie. NT, 2000, XP, 2003) has a MUCH better security model than any UNIX I've seen, OpenBSD in particular.
Are you friggin serious?!?!?
How can anyone honestly say that Microsoft has a better security model? OpenBSD has had 1 root compromise in the default install in 7 years.
Yes, more features, more code, more holes, plain and simple. It's not even that OpenBSD lacks features, they're just not point and click easy, and maybe thats a good thing. It keeps any num nuts with a pirated version of XP (go registration) from polluting the net with another machine just waiting to be owned.

Slashdot Top Deals