I am, meanwhile, frustrated by some of the goings-on at my job. This isn't related to my boss, for a change; it comes to my not being able to figure out a smarter way to do what I want to do. I've got a scheme which works; I just recognize that it's a lousy way to do things, and I'm not having luck figuring out how to make it elegant instead.
The problem is one of XSL transformations, which are these not-really-a-programming-language techniques for starting with an XML document and rewriting it based on the content. What we have are raw data where the descriptions of things are written in numerical codes, and I want to replace the codes with the English-language equivalents (which come from another XML documents, and which I want ultimately to come from a generated-on-the-fly XML because the meanings of the codes can change for some clients). And I want to go through each of the category types and translate the code to its English-language equivalent where that exists, or leave the number unchanged if it doesn't.
I have code which does this; it's just, it has hard-coded in it each of the data properties, which the obviously correct thing to do is write a function which takes as input the property name, and which returns either the translated value or the unaltered code. And that just doesn't work; I get back no response whatsoever. Unfortunately XSL doesn't return error messages, as best I can determine; it just either works or doesn't and good luck finding out why. I'm offended that it's not doing what I want, and that I'm not finding the right level of documentation of XSL to figure out what I want. I suppose it wouldn't really be work if I could just easily pull an example off the web and copy that over, but I like it better when I have the inspiration and it falls into place swiftly.
Trivia: By the end of the 1960s Blue Cross/Blue Shield of Massachusetts had three IBM System/360 computers and a 7074/1401 system to handle its client records, with 43 tape drives in operation. Though COBOL was the preferred language, some programs in the more primitive language AUTOCODER were still used on one of the 360's, emulating a 7074/1401 system. Source: A History Of Modern Computing, Paul E Ceruzzi.
Currently Reading: A History Of The World In Six Glasses, Tom Standage.