greg said:

I'll write a quick intro to what Jim does. Meet Jim:

thanks, greg. but i know what jim does. i've known what jim does for a long time. i'm even one of a probably-small number of people who has gone through the source-code of gutcheck and chuckled at jim's humorous comments there... i'm sure jim does _more_ than i know about, perhaps even more than you know about, greg, but of the things you've told us that he does, all of those are things that _i_ already knew... i don't know how many hours jim spends doing it, but he does _so_much_ that i would be _amazed_ if he wasn't spending lots and lots of hours doing it. i don't know how he finds enough to do it all, frankly. i wasn't knocking jim, and his valuable contributions. but he was knocking me. so i wanted to know why. more to the point, though, i think jim was saying that i don't understand what _everyone_ there does -- not just him personally -- and he might have meant a "mission statement" sense as well as actual tasks. (or maybe not, i'm only speculating.) again, while i am sure there is a dizzying array of a myriad of tasks necessary to keep the big machine whirring away, some of which i am blithely unaware, i firmly believe that i have a _very_ solid grasp of steps necessary to digitize a paper-copy of a book into a full-fledged, high-powered electronic-book, and to do that in the high-volume way intended to create the cyberspace library of the future which will make every book available to every person in every place on the globe at every hour of every day. furthermore, i've had a very solid grasp on all that for several decades now. but i'm still not too old of a dog to learn new tricks, if you can teach any... so teach, if you think there's something i need to learn. because _i_ am always willing to hear someone tell me the things that they think that _i_ need to hear... -bowerbird