Getting distracted...
Jan. 11th, 2015 07:48 pmI started this post earlier in the day with the tantalizing title "Among other idiocy...," but by the time I finally got around to actually applying fingertips to keys, I had completely forgotten what idiocy it was I was prepared to describe.
I managed to finish two jobs today and send them off. That leaves me with the bulk of a third job whose completion date I many have incorrectly estimated because it well and truly contains quite a bit of material.
It occurs to me that one of the more subtle problems I face is the proliferation of document "forks," analogous to the situation that occurs when program source code is diverted for the purpose of creating a similar, yet undoubtedly different version of the program. These forks require additional diligence on my part when attempting to reuse previously translated documents.
I have identified, for example, a "standard" invoice that has suddenly developed a change of telephone number for the seller, among other revisions. And just now, I've noticed that one particular company has apparently adopted language in its invoices that I've seen before, but none of that company's invoices contain it, which means I need to find some other company's invoices to get a running start on translating the new document. In the end, I will either find that language (and hope it's as I remember it, i.e., similar), or I'll have to translate the text from scratch or spend cycles. If I'm lucky, I will be able to find some unique (or nearly so) collocation of words in the new invoice's terms to allow me to sic Google Desktop on the problem to do the dirty work for me.
(Holy heck-of-an-idea, Batman! I just followed my own advice, focusing on the word combination "Economic Court"—as in: "Unresolved disputes between the parties shall be reviewed by the Economic Court in [redacted]"—and found exactly what I needed!)
That done, I must confess to not having found the Post-It with tomorrow's reporting time, so my current plan is to get out of the house early enough so as to be "orbiting" not far from the medical center when I call to find out the actual time I should be there.
Time to wind down. Busy day tomorrow.
Cheers...
I managed to finish two jobs today and send them off. That leaves me with the bulk of a third job whose completion date I many have incorrectly estimated because it well and truly contains quite a bit of material.
It occurs to me that one of the more subtle problems I face is the proliferation of document "forks," analogous to the situation that occurs when program source code is diverted for the purpose of creating a similar, yet undoubtedly different version of the program. These forks require additional diligence on my part when attempting to reuse previously translated documents.
I have identified, for example, a "standard" invoice that has suddenly developed a change of telephone number for the seller, among other revisions. And just now, I've noticed that one particular company has apparently adopted language in its invoices that I've seen before, but none of that company's invoices contain it, which means I need to find some other company's invoices to get a running start on translating the new document. In the end, I will either find that language (and hope it's as I remember it, i.e., similar), or I'll have to translate the text from scratch or spend cycles. If I'm lucky, I will be able to find some unique (or nearly so) collocation of words in the new invoice's terms to allow me to sic Google Desktop on the problem to do the dirty work for me.
(Holy heck-of-an-idea, Batman! I just followed my own advice, focusing on the word combination "Economic Court"—as in: "Unresolved disputes between the parties shall be reviewed by the Economic Court in [redacted]"—and found exactly what I needed!)
That done, I must confess to not having found the Post-It with tomorrow's reporting time, so my current plan is to get out of the house early enough so as to be "orbiting" not far from the medical center when I call to find out the actual time I should be there.
Time to wind down. Busy day tomorrow.
Cheers...