NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
--Larry Wall
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
We started using elog logbooks in a small group (Score:2, Interesting)
We share contacts, project approaches, problem fixes, development ideas, etc. etc. All in a system that is very very simple and easy to maintain.
We can attach emails (or various documents) to our notes, which are uploaded through a standard file dialog to give additional context. The logbooks are fully searchable.
We're supposed to use a Monstrous Problem Ticket/Change Request system for this, but sheesh, it would take at a minimum 3 minutes (vs. 10 seconds for an elog entry) to enter every little note (which couldn't really be cross referenced like elog log entries can - just enter HTML links!), nobody uses it right so you can't really track things with it, the administrator keeps changing the database and screen layout. *shudder* It's a real pain to use.
Thank God for simple solutions that do 90% of what you need. The FINAL TOTAL SYSTEM FOR TRACKING EVERYTHING fits about 40% of our needs and is just too painful to get serious use.
Anyway, we just started, but I'm very hopeful that it'll help us be more coordinated and productive.
Reply to This
Re:We started using elog logbooks in a small group (Score:2)
--Nat
Re:We started using elog logbooks in a small group (Score:1)
The 'pilot' is 2 people. We have adjoining cubicles. There is me and an associate who just started late last year, I've been here almost 5 years. I'm the the more experienced worker, not just here, but overall.
There's a lot to learn on this job. We do 2nd level help desk support troubleshooting for our customer base and development. My associate is trying to learn the ropes, but there's so much work to do that we can't work together on everything. He's taken over cer