| getting technical And life takes another turn. Two weeks ago I started a new job, which is once again taking up time otherwise available for posting. The firm makes software for financial institutions running mutual funds, pension funds and the like. Clients use it to model investment portfolios and to create strategies for neutralizing various forms of market risk. I can't describe anything in detail here -- and your eyes would glaze over if I did -- but the architecture of this strange vessel in which I work is a flowchart: databases, engines, modular bits and other thingummies behind a shiny graphic interface. New components are being added all the time: position-loading is being transformed into XML; yield curves are described; scenarios (or sudden market shifts) modeled. Then another computation engine handles the analytical processes: comparing portfolios to benchmarks, calculating the effect of assorted changes users wish to make to their positions. I'm just responsible for the docs: the user manuals, support and help screens and other technical materials. Translating engineer-speak and (some) financialese into something less arcane. It means using language that is
In the evenings i'm not much good for more than a little browsing and lurking. But my hope is that the daily discipline of writing the technical material will get me back in the habit of producing other stuff. Anyone have a copy of Zen and the Art of Motorcycle Maintenance around? |
return to: Ruminatrix |
"...runo/?/ Content-Length: 0 Connection: close Content-Type: text/html; charset=ISO-8859-1 ..." |