An earth-sized planet around Alpha Centuri. That's old news. I was reading about Adam Strange's adventures on Rann since the early 1960s: http://en.wikipedia.org/wiki/Adam_Strange
I liked Ellison's writing in the 70s but I think his "angry young man" days are long gone. Now he mainly comes off as a "grumpy old man". He's had a reputation as someone who'll sue anyone for anything. Maybe he needs a new hobby. The Star Trek episode in question was filmed decades ago. Nothing more to see here. Move on. Move on.
Agreed. Wikis or SharePoint aren't the immediate answer although they eventually can be part of your solution. The first step is to identify the types of information that need to be gathered and start a process of organization. Develop some sort of framework that you'll put content into when collected.
I had a job working for a bunch of software engineers who didn't have their process documented. Actually, about five different teams had been combined in an enterprise environment and they needed their old intranet sites to be retired, whatever still useful information from those sites to be preserved and a new team collaboration site to be constructed within SharePoint Portal Server 2003. I was tasked with making that happen for them.
Probably the biggest challenge was to get all of the information holders to talk to me and provide me with the information I needed. While they appreciated the fact that they no longer had the burden of writing documentation themselves, they didn't want to take the time out from their projects to work with me. Actually, about half of them were more than available to approach me with their requirements, but the other half needed to be "prodded" into action.
At the end of 9 months, I had their SharePoint site collection constructed and on my last day (sadly, the lot of a contract worker is that you're not forever) I found out that they all very much appreciated the work I'd done, creating the process documentation more or less out of thin air.
Today, I write help documentation for a different software outfit, but I still miss documenting process rather than features. It really is (at least for me) a very satisfying job.
Slashdot Mirror
An earth-sized planet around Alpha Centuri. That's old news. I was reading about Adam Strange's adventures on Rann since the early 1960s: http://en.wikipedia.org/wiki/Adam_Strange
What? Are the light bulb police going to kick my door down to see if my light bulbs meet government standards?
We're in the middle of three wars (including Yemen) but our economy hasn't gotten any better.
I liked Ellison's writing in the 70s but I think his "angry young man" days are long gone. Now he mainly comes off as a "grumpy old man". He's had a reputation as someone who'll sue anyone for anything. Maybe he needs a new hobby. The Star Trek episode in question was filmed decades ago. Nothing more to see here. Move on. Move on.
Agreed. Wikis or SharePoint aren't the immediate answer although they eventually can be part of your solution. The first step is to identify the types of information that need to be gathered and start a process of organization. Develop some sort of framework that you'll put content into when collected.
I had a job working for a bunch of software engineers who didn't have their process documented. Actually, about five different teams had been combined in an enterprise environment and they needed their old intranet sites to be retired, whatever still useful information from those sites to be preserved and a new team collaboration site to be constructed within SharePoint Portal Server 2003. I was tasked with making that happen for them.
Probably the biggest challenge was to get all of the information holders to talk to me and provide me with the information I needed. While they appreciated the fact that they no longer had the burden of writing documentation themselves, they didn't want to take the time out from their projects to work with me. Actually, about half of them were more than available to approach me with their requirements, but the other half needed to be "prodded" into action.
At the end of 9 months, I had their SharePoint site collection constructed and on my last day (sadly, the lot of a contract worker is that you're not forever) I found out that they all very much appreciated the work I'd done, creating the process documentation more or less out of thin air.
Today, I write help documentation for a different software outfit, but I still miss documenting process rather than features. It really is (at least for me) a very satisfying job.