Coding at the mill. I have absolutely no formal education in computer stuff, so all of my learning has been driven by curiosity, experimenting, and browsing the net for resources. And, all this office stuff is so much different from game development, but it has been interesting to learn a bit of this world. Here I'm working with a relational database, writing a piece of software to fetch data and output it to a properly formatted e-invoice xml file. This involves reading the format specifications, where the terminology is somewhat beyond my sphere of understanding, but the way I think about it: it isn't always necessary to fully understand why something works, especially if you can safely experiment with trial-and-error until you get it to work reliably. As, if it works, it works - no matter if you ever fully understood every detail of the xsd schema file, or such - same with so many other things; sometimes getting things to work is the first stage in learning, deeper understanding can mature later on, if necessary. But in my case I have a hunch that developing e-invoicing software is not going to be any of my main projects, so I'm fine with not knowing why it works, if I just get it to do the job. And then I can invest more time in thinking how to best simulate accidents and ailments in an iron age survival simulation =)