What I'm trying to push it to be used for is a repository of information which is currently scattered and unfindable. Example: one of my colleagues wrote a good document about proper grounding practices in industrial IEEE 1394 applications. It was checked into our corporate document management system, where it sits, unused. No one knows where it is or how to find it. It can't be found by casual browsing, or even by a text search, because all that system has for indexing is two 32-char strings for a descriptor. So really, the only person who knows where that doc is and how to find it is him, and he already knows that information. He and I have had a number of arguments about this, as I feel that putting it into a browse-able, search-able Wiki makes it more valuable. He thinks that adding yet another document management system, especially one with no version control, is a needless complication. I have the boss's support, though, and I suspect that over time more and more of my fellow engineers will start using the Wiki. I myself intend to capture as much of the output of stubborn people like this guy and to put it on the Wiki- just because he's myopic on this one issue doesn't mean his information is no good. Mike H. On 4/18/07, Marcel Duchamp wrote: > Help me become tech-savvy. > > What are wiki's used for on the job? > > Mike Hord wrote: > > > Non-tech-savvy folks don't know that our Wiki exists. Truth to tell, the > > big problem here is convincing people to actually USE the Wiki. It > > basically seems to be divided along generational lines and core > > job description lines. Most of the software guys are pretty happy with > > it, but the hardware group seems split by age, with older guys more > > reluctant. > > > > Mike H. > > > -- > http://www.piclist.com PIC/SX FAQ & list archive > View/change your membership options at > http://mailman.mit.edu/mailman/listinfo/piclist > -- http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist