Hello! Do you think your conception of magic in YW is influenced at all by computer code? Between High Wizardry and some of the website admin stuff you discuss here, I'm guessing you've coded at least a little.
I'm an actor-turned-librarian who's cobbled together a little bit of coding competency through goofing off. The other day I tried to explain how I conceptualize a coding project and, well, first you need to figure out something's name -- and make sure you're properly specific for the context, you may need a lot of detail in how you name it -- and then you can start figuring out how to persuade it to do what you want ....
So I guess it's sort of a chicken-and-egg question: have I conceptualized coding in the image of my favorite fictional magic systems, or have I been generally drawn to magic systems with a sort of code-y, process-y inspiration?
I wouldn't like to second-guess your in-brain structure. But I can talk about my historical processes a bit, as they may apply to this.
Let me step back a bit. Before I was a writer, I was a nurse. Before I was a nurse, I was studying to be an astrophysicist. Both of these arts/sciences require a certain sense of the hard structure of the universe—of the ways it requires you to put bits of it together if you're going to get anything useful done. This general outlook has determined, to a certain extent, how I interact with the nuts and bolts of the online world.
Historically speaking: I'm one of an unusual stratum of computer users who were technologically orphaned by the failure of the Osborne computer in the mid-1980s. Those of us who had these machines, and who were at all techie-oriented, quickly became WAY more so in an attempt to keep our Osbornes running after the company went under. We learned how to keep our babies going without any available support, and when we moved on to other machines, we quickly became expert in fixing them... having learned the bitter lesson that when your computer fails, most of the time you're the only one you're going to be able to rely on to keep them going.
We learned to do things for ourselves, from the bottom up: hardware to programming. That mindset has remained with me from then until now.
After my Osborne, I moved from an early Apple (lent by our old friend Michael Reaves) to various early DOS/TRS machines when I moved over to this side of the Atlantic. I wrote STAR TREK: THE KOBAYASHI ALTERNATIVE on a TRS-80 Model 100, gods bless its gentle hardworking heart. (I can still see in my mind the pale, pine-panelled interior of the ancient creaky London hotel, just south of Notting Hill Gate Tube, where I did most of the Trek work while I was in town on other business. I'd hooked the computer's modem to the hotel's phone system with alligator clips.) While Peter and I were later sorting out where we'd live on this side of things, for a long time—before portable computers, except for the TRS—the big machines lived in the boot of the Volvo while we migrated from place to place. And always the alligator clips were there.
Finally we settled in Ireland, and not too long after us, so did the Internet. (But not before I had to go up to Dublin one time, with the alligator clips again FFS!, and show the adorably clueless national telephone company guys how to do it. ...I never pass that building without thinking of it: once Telecom Eireann, then Eircom, then Eir. Now it's a Starbucks. No matter. I remember where to hook the alligator clips in.)
And then, with the internet, lo, there came the (net-oriented) coding. Our first household web site went online in 1995. I handcoded our site's HTML (because what's a girl to do: wait for the boys to make it accessible or affordable? Bwahahahaha). I continued to do that until the early 2000s, at which point I moved our sites to Drupal and learned its obscure ways. These days—having decided that Updating Damn Drupal Core Every Week is not what my mom raised me for—I've migrated all our household sites to WordPress, and I like it. I still pay a lot of attention to them, but at least I don't have to custom-code every whole damn page. I'm happy enough to let Elementor do that, while inserting occasional custom CSS, because (a) I have writing to do, ad (b) Life Is Too Short.
(I also used to hand-build our household computers, because (a) money was short and (b) why not know exactly what all your hardware is? But more recently I've started letting Scan in the UK do that. It's another Life Is Too Short thing... and Scan does good work. Lovely tight builds, and good customer service when needed.)
So: yeah, I code. :) Summing up: I'm fluent in HTML. I'm nearly as fluent in CSS. I have enough PHP to be dangerous (to myself as well as others). I have memories of C that I can dredge up when necessary. I generated most of the Rihannsu language in MS-BASIC, gods bless it. ...And beyond that (as we say around here), deponent saith not. :)
