I was GM and producer for Crudely Drawn Swords, also a horseman, game designer, musician, book fan, pun afficionado, programmer, weirdo know-it-all and occasional wizard. This used to be the CDS tumblr account, but I'm taking it for myself and nobody can stop me, or indeed cares.
Did I mention I have a book for sale? And that it's a fantasy detective adventure story that makes a valentines-day-appropriate hard pivot to romance in the last third?
It also has plenty of content for the mule fans out there, making it the ideal read for anyone who likes mules, romance, or both:
I know what you're thinking: "I do like mules and romance, but I also want to believe that a better world is possible. Is there a book like that which replaces traditional fantasy feudalism with utopian politics?"
Some will say: “I do like mules, romance and utopian politics, but these are heavy topics and I want something easy to read. More of a fast-moving adventure story, perhaps with a kick-ass narrator who makes plenty of jokes along the way.”
I don’t know what to tell you, it’s like I’ve thought of everything.
think there should be an inverse version of htat annoying 'miku made minecraft' bit where you pretend that some extremely evil person made a piece of media you find mildly annoying instead of its by all appearances normal and inoffensive creator
So imagine you go to a brothel and when you get there it’s full of beautiful women but then also there’s this dog. And when you ask “hey what’s with the dog” they’re like oh the dog, we love the dog, everybody loves the dog, the dog collects rocks from the yard. And you’re like “okay” but later you find the dog gathering piles of rocks and cementing them into a beautiful river-stone wall to protect the building. And you’re like “I didn’t even know dogs could do that”. And they’re like “that’s nothing, check this out” and then the dog starts doing multiplication with the rocks. You’re like “what the fuck” and they go “nahh she’s just getting started”. And they start giving the dog complex mathematical formulas that the dog answers by laying out the rocks. And you go “holy shit that’s the smartest dog I’ve ever seen”. And they go “it’s the smartest dog in the world” and you’re like “wow that’s amazing”. And then you look outside and the dog is eating the rocks. And you’re like “can the dog eatrocks?”. And they’re like “no”
One day you find out the dog went missing. “We don’t know where the dog went but we miss the dog”, the beautiful women tell you. A year later the dog comes back. The dog is accompanied by the Duke of wales. “My gardener stole this dog but now I would like to buy it”, he says. “The dog has built me a beautiful castle and solved the viscount’s mysterious murder.” You aren’t sure how the dog did that by stacking rocks but you’re still incredibly impressed. The beautiful women are so happy to see the dog again. “Did you know that the dog can ride a bike?” The Duke asks. You look at the dog. The dog is obviously concealing a mouth full of gravel
This is the post that enticed me to watch apothecary diaries and now that I am watching apothecary diaries I am constantly pointing at the very deliberately cat-coded character, whose name is 'cat-cat', and shouting 'this dog can EAT ROCKS?'.
I’ve gotten so many messages about this post because Maomao is EXPLICITLY cat-coded with cat motifs and cat associations with cat jokes but the truth is there was no energy I could think of that captured her baffling aura like a large old farm dog dog eating a rock. Cat eating plastic? Cat opening doors? Cat eating legos? No, she is my grandpa’s very clever old sheepdog who would roll his eyes at you and tiredly and patiently perform very human tasks as you asked him to like a 56 year old underpaid chain-smoking senior retail colleague and then turn around and try and eat a rock. In a world of elegant show-breed cats she is a cat yes but also The Most Dog cat there ever was. And she’s eating rocks
Yeah actually, one day you give the dog a bath and it’s the most majestic giant Norwegian forest cat you’ve ever seen in your entire life. But☝️it’s still an absolute FIEND for eating rocks
Standard sword and sorcery fantasy film periodically interrupted by cutaways to an in-universe historian from a notional period hundreds of years after the depicted events explaining the film's various historical inaccuracies. There's a recurring tangent about how the film's protagonist is a conflation of three different guys, all of them much weirder than the end product of that conflation.
At one point the historian remarks that the film's principal villain probably never existed, but you can tell from their thousand-yard stare that there's some Poe's Orangutan level discourse about that topic.
Standard King Arthur movie with the usual ‘back in the 6th century…’ establishing blub, which looks a little odd because it started with a specific year, which was crossed off and replaced by another, which was also crossed off and replaced by ‘~6th century, give or take’ along with a few other editorial addendums.
Opens with Uther and Merlin discussing the siege of Tintagel. Things go smoothly until Uther’s name is used, cue the first interruption to explain that Uther was probably an ‘invention’ of Geoffrey of Monmouth, but then that academic is interrupted by a Geoffrey apologist (possibly yours truly) to defend his work with a complicated spiel that gets interrupted by the actor who plays Merlin insisting ‘we should get back to the story’
What follows slowly unravels into a poorly disguised academic debate mediated by the Merlin actor as the voice of ‘well I was actually There!’ And it slowly becomes clear that not only does he genuinely believe he’s Merlin, but his version of the story is absolutely the most unhinged and least academically supported version and relies largely on the French Romances for some reason*.
*the reason being that this is an accurate representation of many fans, who hold the Romance era as the ‘Cannon’ for King Arthur even knowing it is not the ‘Historical’ or even ‘Original’ narrative.
“The cannons of his adversary were thundering in the tattered morning when the Majesty of England drew himself up to meet the future with a peaceful heart.”
it's fun to draw the realis pcs because i haven't looked for other people's designs and gone 'that's perfectly what they look like in my head now' yet (but i hope i will, i love to see them)
The current Realis episodes from Friends at the Table are as strange and dark as anything they’ve done and I wanted to try and capture that but the side of my brain that does the drawing had other ideas.
As a Computer Toucher and Horse Person I can confirm. Typically with a computer you have to figure out how the seemingly bizarre behaviour is following an underlying logic, with horses it’s a question of how to work through a million years of survival instinct and emotion to teach them how to work logically. Both are fundamentally about understanding and problem solving, but horses will always be closer to my heart.
Code is a liability (not an asset). Tech bosses don't understand this. They think AI is great because it produces 10,000 times more code than a programmer, but that just means it's producing 10,000 times more liabilities. AI is the asbestos we're shoveling into the walls of our high-tech society:
Code is a liability. Code's capabilities are assets. The goal of a tech shop is to have code whose capabilities generate more revenue than the costs associated with keeping that code running. For a long time, firms have nurtured a false belief that code costs less to run over time: after an initial shakedown period in which the bugs in the code are found and addressed, code ceases to need meaningful maintenance. After all, code is a machine without moving parts – it does not wear out; it doesn't even wear down.
This is the thesis of Paul Mason's 2015 book Postcapitalism, a book that has aged remarkably poorly (though not, perhaps, as poorly as Mason's own political credibility): code is not an infinitely reproducible machine that requires no labor inputs to operate. Rather, it is a brittle machine that requires increasingly heroic measures to keep it in good working order, and which eventually does "wear out" (in the sense of needing a top-to-bottom refactoring).
To understand why code is a liability, you have to understand the difference between "writing code" and "software engineering."
"Writing code" is an incredibly useful, fun, and engrossing pastime. It involves breaking down complex tasks into discrete steps that are so precisely described that a computer can reliably perform them, and optimising that performance by finding clever ways of minimizing the demands the code puts on the computer's resources, such as RAM and processor cycles.
Meanwhile, "software engineering" is a discipline that subsumes "writing code," but with a focus on the long-term operations of the system the code is part of. Software engineering concerns itself with the upstream processes that generate the data the system receives. It concerns itself with the downstream processes that the system emits processed information to. It concerns itself with the adjacent systems that are receiving data from the same upstream processes and/or emitting data to the same downstream processes the system is emitting to.
"Writing code" is about making code that runs well. "Software engineering" is about making code that fails well. It's about making code that is legible – whose functions can be understood by third parties who might be asked to maintain it, or might be asked to adapt the processes downstream, upstream or adjacent to the system to keep the system from breaking. It's about making code that can be adapted, for example, when the underlying computer architecture it runs on is retired and has to be replaced, either with a new kind of computer, or with an emulated version of the old computer:
Because that's the thing: any nontrivial code has to interact with the outside world, and the outside world isn't static, it's dynamic. The outside world busts through the assumptions made by software authors all the time and every time it does, the software needs to be fixed. Remember Y2K? That was a day when perfectly functional code, running on perfectly functional hardware, would stop functioning – not because the code changed, but because time marched on.
A big reason why some people think chatbots are great at writing code is because it's like gambling. Entering a prompt and having a chatbot return in seconds workable code that would have taken you hours to write is like hitting the jackpot on a slot machine, it's an incredible rush. Gamblers remember the times they hit a jackpot but ignore the fact that they lost money overall.
This is how you can end up with coders insisting that AI tools benefited them in a study proving that AI tools made them less productive.
Even worse, Im in a lot of open source code related spaces and if you don't ask a chatbot for help before asking people, no one helps you nowadays like 60% of the time.
Its like going to a doctor and being like "Im coughing up blood" and they respond with "well have you tried the slot machine yet? You should try the slot machine before you ever speak to a doctor".
I got laid off recently. I'm a data engineer by day, one that is exceedingly vocal about how unfathomably dangerous AI can be, will be, already is, and has been for several years. We're all beginning to feel it--I'd argue we've been living it since 2015, but that's an adjacent albeit highly related topic--and now AI is not only the reason but the scapegoat for so much heinous corporate behavior.
I was forced to use Copilot--Microsoft's built-in AI--in my day-to-day work last year. Without diving into too much of my history at this employer (lots of reorgs and different managers because the company had 0 clue how to support a data warehousing team that was solely responsible for internal employee data), I got a new manager in January of 2025 and shit went south fast.
I couldn't just not use Copilot either. Microsoft has it's grubby little fingers all over the usage of your computer, as mentioned in Corey's essay above. Managers are provided with usage metrics, down to keystrokes and mouse clicks, of their direct reports. Microsoft uses this as a selling point to corporations. And they love it.
So I couldn't lie. I had to use it. And every time I did, I wasted so much time arguing with it, prompting it, finding ridiculous uses for it, vetting that it did what I wanted it to do, redoing all the work it half-accomplished or hardly-at-all accomplished. I gave this information to my manager regularly. My ex co-workers rarely helped me when I asked them how they were leveraging it so well; I'm convinced they were over-hyping it to protect themselves.
By the summer, my new manager was getting on my case about it. Not using as much as my peers, there has to be ways I can leverage it. I tried. I threw all of my work at it, but it was never as useful or accurate as I was. Sure, I was slower. But my work, my code or workflow or ETL or whatever it was, was correct. Accurate. Copilot regularly spit out garbage. And my manager didn't care. By November, I was out. I later found out my team was shocked. My previous manager was baffled. All of the people I'd worked with outside my team were stunned.
It's not because I didn't use AI well. Corporations like to do end-of-year layoffs to reduce headcount so their bottom line looks better. Less liability. That's the core of it. Economy sucks, bottom line looked bad, everything costs way too fucking much, and to keep people even remotely interested in barely working, their salaries have to barely make ends meet. So layoffs are inevitable. But the messaging that the company put out was that AI had made IT more efficient so they could do more with less. And that's the story the tech sector has been bandying about since 2024, laying off hundreds of thousand of highly educated, experienced developers in just two years. And we're being told to learn AI because it's going to fix everything.
It cannot. It will not. Code is not an asset. It is a liability. And AI is only going to make it lethal.
I have a simple theory about why some people think AI is amazing for programming and others hate it: By definition what an LLM stores in its training data is the average of what it found on the internet. That means if you’re a worse than average programmer it will feel like a big improvement. If you’re better than average it will feel like a drag.
I don't often share real life things here, but here's a Mari Lwyd to wish you a happy new year (and for good luck). Maybe 2026 will be the year I learn to mesh and finally make myself a Mari in game, because what do you mean we don't have one yet 🥲🥲
“That’s why it’s hard to make friends when you’re older,” she said. “Friendship is rude.”
Her friend’s eyes widened. “What?”
“Think about it! When we’re kids we decide who we like and stick by them no matter what. As adults, we’re taught to be polite.
But, friendship is an imposition— at least, I want it to be. Call me after nine o’clock. Don’t think you’ll ever wear out your welcome. Overshare, show up at my door, go to the grocery store with me so we can waste another hour chatting.
We’ll never be friends if we spend all of our energy trying not to bother each other.”