Now I have a good handle on how the previous programmer typically mucked things up, it’s becoming much simpler to predict what they omitted or their weird ways of implementing otherwise ordinary procedures in a semi-sane fashion.
The time to convert a report from a format intended to be rendered on a specific brand of dot-matrix impact printer to a generic prints-everywhere email-able PDF file (via an HTML-ish file) has decreased from several hours per report to maybe half an hour... & shrinking...
Call it “meta-study,” in that instead of attempting to divine how something was done each time, one figures out roughly why certain things were done in certain ways, then the discrepancies often make a bizarre kind of sense, & can be rapidly, systematically replaced with much more concretely sane ways of doing things.
The time to convert a report from a format intended to be rendered on a specific brand of dot-matrix impact printer to a generic prints-everywhere email-able PDF file (via an HTML-ish file) has decreased from several hours per report to maybe half an hour... & shrinking...
Call it “meta-study,” in that instead of attempting to divine how something was done each time, one figures out roughly why certain things were done in certain ways, then the discrepancies often make a bizarre kind of sense, & can be rapidly, systematically replaced with much more concretely sane ways of doing things.
Comments