Wouldn't it be grand if we had an honest enough industry that you could tell the truth about how previous projects went, consistently? Every time I've screwed up, I've learned something, either about myself as an engineer or about project dynamics, and I really hope I apply it. I'd rather hire and be hired by other people who understand that we are both aiming for consistent success and learning from failure, and who are honest enough to own it.
I had to smile at this. Stuff like this happens all the time. But I'm kind of surprised that the bug was incorrectly pri'd and ignored through how many triage meetings? I don't know many test or dev pms who would blow off a complete review of all current bugs regardless of status or assignment...and certainly as responsibility rises, there are more people willing to crawl that list, ad naseum.
1. Get the profs to do it in a digital format, _any_ digital format that can be scrolled -- ideally something which can incorporate diagrams and equations, but really whatever the default IT word processor is, or if individual, work with them -- because the result, from the experts themselves in a searchable "hands on" format, will simply be an order of magnitude better than anything you can scan in and attempt to make searchable. 2. Look for local scanning firms. We just finished a 15,000 page run for a client via a local legal dbms firm here in town (Seattle) for.10 a page, in PDF format at 600 DPI. We spent almost as much "coding"(in the paralegal sense) the documents into a sharepoint list. 3. Scan and bear it. You are right, unless you have been very lucky in choice of scanners and the people involved didn't wrinkle the sheets too much, it is going to require an attentive human monitor.
Slashdot Mirror
Wouldn't it be grand if we had an honest enough industry that you could tell the truth about how previous projects went, consistently? Every time I've screwed up, I've learned something, either about myself as an engineer or about project dynamics, and I really hope I apply it. I'd rather hire and be hired by other people who understand that we are both aiming for consistent success and learning from failure, and who are honest enough to own it. I had to smile at this. Stuff like this happens all the time. But I'm kind of surprised that the bug was incorrectly pri'd and ignored through how many triage meetings? I don't know many test or dev pms who would blow off a complete review of all current bugs regardless of status or assignment...and certainly as responsibility rises, there are more people willing to crawl that list, ad naseum.
Quick suggestions:
.10 a page, in PDF format at 600 DPI. We spent almost as much "coding"(in the paralegal sense) the documents into a sharepoint list.
1. Get the profs to do it in a digital format, _any_ digital format that can be scrolled -- ideally something which can incorporate diagrams and equations, but really whatever the default IT word processor is, or if individual, work with them -- because the result, from the experts themselves in a searchable "hands on" format, will simply be an order of magnitude better than anything you can scan in and attempt to make searchable.
2. Look for local scanning firms. We just finished a 15,000 page run for a client via a local legal dbms firm here in town (Seattle) for
3. Scan and bear it. You are right, unless you have been very lucky in choice of scanners and the people involved didn't wrinkle the sheets too much, it is going to require an attentive human monitor.