Comment Oh sure its ok for Corporations... (Score 1) 553
If the government did this, it would be called "Socialism". I guess its ok for Corporations to do this sort of thing.
If the government did this, it would be called "Socialism". I guess its ok for Corporations to do this sort of thing.
Moon all the way. We need to mine some of that yummy Helium-3 so we can finally move forward.
Totally agree. What we have done is have the location, rack, elevation, and purpose in the naming convention for the hardware as well as documenting what that all means in human terms.
Roff and grep are neat if you know which files to grep from, where they live AND what to look for. Companies like Splunk are making money for a reason; i.e. sometimes you need the latest version of everything available for you at a moments notice when it is 3am and your production network is on fire and your boss is over your shoulder screaming at you and customers are on the phone all pissed off, etc. etc. Having a readily available, up to date, single source database of readable information takes the edge off. How do I know? I've been there many times my friend. As far as my credentials, I won't respond to a troll about that.
Wiki's work, but I am thinking more along the lines of Lucene where you can point it at existing data without much effort. Assuming config changes, cert and license data and network diagrams have usable text already associated with them, you can save a great deal of time just indexing what you have.
For me, visio's are great and everything, passwords too, but really the most valuable thing you can do is document single points of failure, outdated software/hardware, etc., license keys/expiration dates, cert expiration dates, personal support contacts you have and all vendor relationship details as well are essential. Do you use change control? If you do, go back and comment your changes, if not, do the best you can at explaining why things are the way they are. Get some open source software that is good at indexing data and create a searchable knowledge base from the information above. Don't concentrate on docs that can be found on the web at first because any admin worth their salt will know where to look for how to's, etc. Focus on the why's, the where's and disaster recovery.
My two cents...
One hundred million years ago a termite was wounded and its abdomen split open
That would make a better film than most of the crap out there at the moment.
Heh sounds like the beginning of an 'Alien' sequel.
As a developer, I say that surely it's the tester's fault if there's flaws!
Funny, and true. Its all about resources and piorities. Huge companies like Microsoft really have fewer excuses given the amount of resources they have to create and release good stable code. As far as priorities are concerned, if your huge budget is spent on marketing and new features but lacking in resources to make the existing product stable, then the threat of a lawsuit may just re-align those priorities.
As far as free software (GPL) is concerned it is your duty to report bugs back to the community and even fix them if you have the skills. Open source by nature is "QA'd" by the community which in turn can make a more stable (read: Linux, the Gimp, etc.) product in the long run. To put it bluntly, who are you going to sue, the whole open source community?
In conclusion, closed source should not be exempt from this, but open source is. Who's with me?
Top Ten Things Overheard At The ANSI C Draft Committee Meetings: (5) All right, who's the wiseguy who stuck this trigraph stuff in here?