I have a-maze-ing ideas. They're not good, but people who hear them often feel like they're trapped in a labyrinth without hope of escape.
Trying to hedge my bets, here.
I have a-maze-ing ideas. They're not good, but people who hear them often feel like they're trapped in a labyrinth without hope of escape.
Trying to hedge my bets, here.
The progression of my opinion on AI has been ... elliptical? Not straightforward, we'll say. But as I've gotten to use it more, both at work and through some of my own personal projects, I've started to see where some of the dissonance, I think, lies – both for me and others.
To back it up, I want to talk about software personalization. Since punchcards, people have written new programs because the program they were using had something wrong with it. Did it let you type into the screen and print out what you see? Sure, but we still had Microsft Word. Microsoft Works. Pages. LaTeX. WordPerfect. WordStar. Claris. Lotus. WordPad. TextEdit. Notepad.
Software, at its best, is thinking embodied through code. It should allow you to do whatever you were going to do, but better and faster.
In my past life, when I was the only person who knew how to code in an organization, that was literally my favorite thing about being a software engineer. I could go in, get a problem from someone, help them solve that problem through software and end up feeling like I built something and I helped them. That is literally why I became a software engineer.
And the reason we want to personalize software is because everyone works differently. You cannot just throw a general piece of software at a specific problem and expect it to work. Despite how expensive ERPs like SalesForce, etc., are, every decent-sized implementation requires the end-user to hire a developer to make it work the way they want to.
And they do it because software is expensive! Even buying into fancy, expensive software is cheaper than building in your own.
Or at least, it used to be.
Now, on a personal level, I strive for efficiency. I am unwilling to admin how many e-readers and tablets I have purchased (and re-purchased) to find the, "perfect method for reading." Oh, Kindle won't read epubs. Oh, the Kobo is a pain to sync new files onto if you don't buy them through Kobobooks. Oh, the eInk Android tablet works slower because it's Android trying to run on eInk. Oh, the iPad is too distracting. Oh, the Kindle ...
I don't think the problem is the device or the software. It's my mindset.
And I think everyone's got at least some piece of their life that works that way – or they've gotten lucky enough to find the thing that works for them, and they stick to it. This is why so many people wind up with clothing "uniforms" despite not being mandated. How many people have bough multiples of an item because you don't know if it'll be available the next time you need to get a new one?
And to be honest, that's how I still see most of AI's generative output, at least when it comes to purely creative efforts like writing or other content creation. It's trying to appeal to everyone (becuase it literally is sliced chunks of combined consciousness).
And as an engineer, when I used some of the coding agents from even six months ago, I saw much of the same thing. Sure it could churn out basic code, but when it tried to do anything complex it veered too hard toward the generic, and software engineering is a very precise arena, as anyone who has forgotten to add or remove a crucial semicolon can tell you.
But then at work, we started to get more tools that were a little bit more advanced. They required more planning than when I had been trying to vibe code my way through things. I was surprised at how nuanced the things our new code review tool could catch were, and the complexity of rules and concepts it checked against. And I started to realize that if we were using AI in conjunction with existing tools and putting in the level that I would put into normal engineering, I could start to get some pretty cool stuff.
A quick digression into the past. I previously tried to build my own CMS. I think everyone has at one point. For about the first three or four days, it was an earnest effort: "I'm going to build this and it's going to be the next WordPress."
I quickly realized one of the reasons WordPress sucks so much is it tries to be everything for everyone and therefore it's just winds up being a middling ball of acceptable. (Especially when they got confused as to what they actually wanted to be – a publishing platform or a Substack alternative or a Wix competitor. Gah, no time to fight old battles.) Again, trying to be everything for everyone winds up in the software usually working poorly for every individual.
So I was like, I'm going to build my own CMS. And I built it. And what it ultimately wound up being was an object lesson in why frameworks (e.g., Laravel) tend to be structured the way they are. It was super useful for me as an engineer because I got to see the process of building this large piece of software and think about things like modularity, how to enable plugins you can easily fit into to an existing system. Legendarily helpful for me from a learning-how-to-architect standpoint.
But from an actual usability standpoint, I hated it. Absolutely abhorred using the software.
I spent about 14 hours yesterday of intensely planned vibe-coding. I had my old blog, which was built on Statamic, so I had an existing content structure that Claude could work on.
And I walked that AI through half a day of building exactly the content management system that I want, both for my personal note storage and this blog (which is actually now powered by that same CMS). It took me about two hours to replace what I already had, and the rest of the time was spent building features I've been planning in my head for years. And the UX is surprisingly polished (and weird) because I want it to be polished and weird. It is customized software, fit for exactly my use case.
Originally I thought, "I'm going to build this thing and I'm going to let everybody use it, whoever wants to use it." But as I kept blowing through features I've been salivating over, I realized: I don't think anyone else would want to use this. They would say, "Hey, those are some cool ideas, but I would love it if it did this." And I have absolutely no interest in sitting through and helping somebody else work out how to make their version of this thing – unless they're going to pay me for it as a job, of course.
In an abrupt change for myself, I am now willing to vocally get behind that idea that AI can be used to build good software. But I am going to be adamant about that crucial "used to build" phrasing: I do not believe AI can build good software on its own. I think it can be used as a tool: Software engineers can use AI to build exactly the software we wanted.
None of the stuff it did was beyond my technical capabilities, it merely exceeded my temporal capacity: Stuff I didn't have time to do.
What's especially funny to me is that the best analogy I have for the utility of AI (and this may just be a function of my career history as an engineer): It is a low-code coding tool for software engineers.
We did it, everybody! We finally managed to build a no-code tool, but it's still only functionally usable by engineers.
Every time I’ve tried to involve AI in one of my creative pursuits it has spit out the exact same level of meh. No matter the model, no matter the project, it simply cannot match what I have in my head. Which would be fine, but it absolutely cannot match the fun of making the imperfect version of that idea that I may have made on my own either. Instead, it simulates the act of brainstorming or creative exploration, turning it into predatory pay-for-play process that, every single time, spits out deeply mediocre garbage. It charges you for the thrill of feeling like you’re building or making something and, just like a casino — or online dating, or pornography, or TikTok — cares more about that monetizable loop of engagement, of progress, than it does the finished product. What I’m saying is generative AI is a deeply expensive edging machine, but for your life.
…
If we are to assume that this imagination gap, this life edging, this progress simulator, is a feature and not a bug — and there’s no reason not to, this is how every platform makes money — then the “AI revolution” suddenly starts to feel much more insidious. It is not a revolution in computing, but a revolution in accepting lower standards.
I recently stumbled on a serialized webnovel (that I will not name for reasons that willl soon be clear), and got invested. I mean like, invested. I was reading it nonstop, blowing through the first 300,000 or so words (of the total ~1.6m) in about three days.
The characters were quirky, if sometimes missing their specific characterization and instead acting in accordance with the plot rather than their own internal narrative. The story was interesting (think geting dumped into your own D&D game and needing to survive), along with plenty of meta-commentary and humorous bits that kept my interest.
It was about the 300K mark that I realized I was reading a Rationalist novel. I finally twigged after one-too-many cutscenes where one character would word-vomit up a strawman situation only to be Rational-splained about it before I finally picked up on where the weirdness lay. I don't have a problem, per se, with Rationalist content, though in my experience it tends toward boring, repetitive and (often) condescending explanations of questions that no one asked. I'm legitimatley not trying to slag on it, merely giving you my history with it.
It wasn't enough for me to give up on the book, because I was still enjoying myself for the most part and the author seemed to be aware of some of the failings of pure Rationalism (that I have zero desire to discuss further) and specifically noted them.
200K words later, my favorite character had an out-of-character-for-her interaction and promptly died. Sure, it was in service of the plot and, yes, we did have the subsequent Fridging discourse (again, very meta novel). I was very much on the edge of putting the book down. I looked up to see whether the character would be revived (very doable in a LitRPG), and saw that they did come back, which ameliorated my anger somewhat. I was still a bit apprehensive but chose to move on.
Two pages later, the protagonist talked about statutory rape he committed before getting sucked into the game world, and I prompt deleted the book from my ereader.
I wrote out my thought process mostly to show that it was a difficult decision to abandon a sunk cost of 5-600K words read. It felt like something of a waste. But it's important to remember that there are so many good books/TV shows/movies out there, you have absolutely no need to stick with media that for whatever reason (content, authorial dickishness, price increases) you no longer find joy from. It's perfectly acceptable to set media boundaries and enforce them; doing so doesn't make you any less of a fan/reader/viewer.
I love the concept of reviews. To me, it’s creating art in response to art, which – as a person who struggles to “create”art from nothing, who is more comfortable editing and remixing and iterating – is the highest form of art I see myself producing.
But reviews have so many jobs to do. They have to establish the credibility of the author to even be reviewing the material (“who the fuck are you to criticize someone who can actually create?”). They have to convey the author’s feelings about the art under consideration. And they also have to be well-structured and well-crafted enough to stand on their own - after all, the vast majority of criticism is read by people who have not yet (and, in all likelihood, never will) experienced the original work themselves. And, bonus, if it’s a rave, I believe the critic owes a responsibility to find a way to convince more people to experience it on their own.
But reviews are also so much, always, about the reviewer as much as the title under scrutiny. Only a fool or a narcissist believes themself an objective arbiter of taste or quality, and so the reviewer must grapple with how much to reveal. Hide behind too many academic terms or in-depth readings and you lack vitality and relevance to anyone worth knowing or interacting with.
I am writing this alongside my review of The Three Lives of Cate Kay, because the book hit me I’m sitting at an outdoor cafe on the dock while the boat from Speed 2 is bearing down, except I’m actually in a Final Destination movie. There is no escape. Every dodge, every distraction only seems to bring it barreling toward me ever faster, looming ever larger.
I don’t feel destroyed by this book, I feel deconstructed into component parts laid bare. I need to have this wholly separate piece of work so that I might start trying to gather those pieces together, while still trying to write a useful review of the book that can do even a shred of work toward pushing people to read it. I feel like my various internal organs are scattered at my feet, and I need to step thoughtfully among them in order to write something important (to me), while taking care not to step on anything important.
I know this book is already somewhat to actually popular, so my piddly efforts amount to very little in terms of getting more people to read the book.
But to me, the act of reviewing is also reaching out, trying to connect. To show through my art (the review) how this art (the book) made me feel, so that we (whoever you are) might be able to connect in some small way, to feel less alone. Yet another job on the pile, I suppose.
Thank god I already had my gallbladder removed, or I might have had nowhere to walk.
I implore you to violently ignore the synopsis below. It's so ... wholly inadequate to what this book holds, it honestly makes me want to scream a little bit.
All books that resonate with me do so because I can see myself in them, in some way. This is why I tend to be drawn to autistic characters – that small delight of Hey, I do that!, the delightful little gasp of representation.
But I probably go overboard, too? As anyone who interacts with me can attest, when I hit the "all is lost" dip of most modern romances, I will become broody and irritated. I inhabit the books I read, somewhat unhealthily so at times, and I find myself almost sad sometimes to come out of it when everything magically resolves itself.
Then I read something like The Three Lives of Cate Kay, and I walk around feeling like I have a javelin jutting out of my stomach - painful, to be sure, but also just constantly, irritatingly In the way of what I'm trying to do. Knocking over the bottle of water I want to drink (that would probably just burble out again anyway), a minor annoyance on top of a gaping, possibly mortal hole in my torso.
This book was infuriating! I employ no subtlety in my dislike of writers writing about writing, the "cheat code" because you know I love books because I'm reading a book. And yet! While I didn't find the excerpted passages of the book-within-the-book particularly inspriing, I for the first time found some compassion in it? Because the reason Cate Kay is an author is because of how she relates to books, how it feels to read them and the joy from writing.
Hell, by my own measure I'm cheating just by writing book reviews, because if you're reading this you probably like reading too, right?
This book is difficult. It is not a standard romance - barely romance at all, really. It's a love story, though, a beatiful, damaged, tragic and not inspiring but fucking wholesome love story. It's love as it's lived, rather than love as it's imagined on the page.
I'm not going to bother to try to recap the plot, as it's too intricate to try to contain concisely. It's written as a joint memoir, a Rashomon look at various pivotal sections of the author's life through the people who were involved. They're all fully human characters, by equal traits amazing and yet still as flawed as the rest of us. Each one felt like someone I could run into on the street or perhaps punch in the face, as the situation warranted.
I don't think you're going to react to this book the same way I did. But I think it might get you, maybe in a similar way or on a wholly different wavelength. And if it doesn't, I hope you find something that does. This is art at it's finest - communicating a feeling – no, broadcasting a feeling, that may resonate far beyond after the last page has been turned over.
Cate Kay knows how to craft a story. As the creator of a bestselling book trilogy that struck box office gold as a film series, she’s one of the most successful authors of her generation. The thing is, Cate Kay doesn’t really exist. She’s never attended author events or granted any interviews. Her real identity had been a closely guarded secret, until now. As a young adult, she and her best friend Amanda dreamed of escaping their difficult homes and moving to California to become movie stars. But the day before their grand adventure, a tragedy shattered their dreams and Cate has been on the run ever since, taking on different names and charting a new future. But after a shocking revelation, Cate understands that returning home is the only way she’ll be a whole person again.
There's a particular kind of narrative laziness that irks me. Not enough to hate the work entirely, but it .. disappoints? Me every single time.
One of the reasons I did not fall headfirst into Sherlock when it first exploded onto the cultural landscape was a bit of the same thing. The first episode (spoilers) involves trying to deduce what happens to a woman, and Holmes uses a number of clues not actually discernible through the camera in order to solve the mystery.
And that's ... fine? If your story is about the relationship between Watson and Holmes and Holmes trying to figure out how to interact with the world, the mystery matters less. But in the pilot episode, you probably have to not focus so intensely on the mystery if that's what you want me to take away from it?
(I'm getting there, I swear.)
I actually came into this book blind - didn't read the blurb, knew absolutely nothing other than the fact I've liked some of the author's previous works (and profoundly disliked one or two). I think there was some benefit, there – I wasn't expecting too much and, despite being a little annoyed to find out the eponymous devil is a literal demon, I was able to settle in.
Overall, the story is a decent Twilight Zone episode, with the main character, Samantha, trying (and failing) multiple different ways to get back the girl of her supposed dreams afrer whiffing mightily with a romantic dinner proposal. Sam's development (and realization of precisely how she got so entangled with this woman) are astute and not a vein of characterization I've seen in a lot of romance novels.
And Daphne, despite some somewhat dated references (that landed perfectly for me, a dated person in her own right), was witty and relatable.
My gripe comes with the ending. I won't spoil it entirely, but the denoument comes through a MacGuffin we only discover even exists once it's been activated and saves the day. It's fine, drawing on cultural tropes and expectations, but in a "beating the devil" romance narrative, I'd like to see more thought put into it than straight-up stealing the major plot point from This is the End, the stoner comedy apocalypse film from 2012.
A fun read, but don't expect a narratively satisfying ending.
Samantha Cooper is having a day from hell. In less than 24 hours, her life has unraveled, leaving her single and with nowhere to live. Adding insult to injury, she’s trapped in an elevator with a gorgeous woman claiming to be a demon. Daphne is not at all what Samantha expected from someone claiming to be an evil supernatural entity. She’s pretty, witty, dressed in pink, and smells nice. And she’s here to offer Samantha a deal she can’t refuse. Six wishes in exchange for one tiny trade—Samantha’s soul. There’s a glaring loophole in their contract, one Samantha fully intends to exploit so she doesn’t fork over her soul. After all, she only needs one wish to win her ex back. Hell-bent to gather the last of the one thousand souls she needs so that she can be free of her own devilish deal, Daphne grants each of Samantha’s wishes . . . with a twist, so that Samantha is forced to make another. As Samantha’s wishes dwindle and Daphne offers her glimpses into the life she *thought* she wanted, the unlikely pair grows close. Perhaps the girl of Samantha’s dreams is *actually* the stuff of nightmares, but Samantha and Daphne will have to outsmart the Devil himself if they want a chance at happily ever after.
I have made no secret of my displeasure with a lot of the hype and uses for AI. I still feel that way about a number of things that AI is used for, but I've also found some areas where it has shown some legitimate use-cases (the automated code review we're using at work as part of a larger, human-involved code review process frankly blew me away). As a result, I'm trying to stay open-minded and test out various scenarios where it might be beneficial to me.
I created a small Gemini gem to automate the process of making book quotes. My rationale here is that the alternative is my manually creating them in an image editor (and I never feel like going through all the effort). It's not taking away the work of a human except my own, and the artistic expression is about as much as I want.
I really wanted to automatically include the cover of the book, but the current version of Gemini doesn't have that ability - I'd have to upload the cover manually, which is the sort of effort I'm trying to avoid. But it did offer to try to recreate covers manually for me, and then use the accompanying representation.
I'm not gonna lie, I almost went for it. It's close enough to impart the general idea of the cover, and for a minute I was even tickled by the idea of having custom covers for the books, similar to the generated UX I keep hearing lurks just minutes away from sweeping away all design, ever.
But upon reflect, that's just a bit too far for me. Those covers were (hopefully) made by humans with an artistic eye and vision they were trying to impart, and to replace it with an AI imitation is to cheapen their work and lessen the impact of it.
It is, however, super annoying that this version has a much better layout overall.
Caveat: Nieman is absolutely crazy to think that generative UX is happening anytime soon, given how often people fail at basic, human-designed UX. A guaranteed way to piss off every one of your users.
Nostalgia for the current moment is, I think, a staple of the modern era
I like how Wicked: For Good ends with Elphaba and Fiero, a green lady and a man made of straw, are traveling to (presumably) earth. Where no one’s ever had trouble because of their skin color or looking different
Also, the new songs added to extend the runtime were not good, but mostly because they didn't really let them sing the words?
Saw Twenty-Sided Tavern at the Balboa last night. This is immediately after the DM (the woman in purple) rolled, with disadvantage, a nat 1 AND a nat 20.
Saw Twenty-Sided Tavern at the Balboa last night. This is immediately after the DM (the woman in purple) rolled, with disadvantage, a nat 1 AND a nat 20.
I’m not sure if this is a special section or an ongoing series, but it’s basically the entire who’s-who of good digital journalism of the 00s/early 10s. Mostly I’m just mad about how difficult it is to find the work of most of them nowadays.
I love @catieosaurus, even if a lot of times it seems like she's yelling at me
I think we're all aspirational, in different ways. There's always a goal we're striving to accomplish, be it academic, professional or personal.
When I was a kid, I wanted to be a teacher, having admired those who taught me during school. I also wanted to lose weight (hello, internalized fatphobia!), be a comedian (CHECK) and I was constantly starting (and never actually writing in) a journal.
Buying new notebooks? Sign me up! Clearly the only thing preventing me from writing in them was having the wrong journal. And then the wrong pen. And then the wrong writing setup.
It took me a while to realize I'm just bad at written introspection. But I always saw the possible utility of journaling, writing down the minutaie of your daily life for later perusal (for whatever specific need!).
I Hated You In High School **is kinda thumbing its nose at me, but it's hard to argue with success. Tessa doesn't remember exactly why she hates Olive, her one-time high school confidante. She just remembers the bad vibes.
But luckily, Tessa is a cartoonist! So we get to see the cartooning journal she kept that lays out all the excruciatingly gay teen agony that caused the upset in the first place. And of course, there'd be no reason to be reliving all of this if there weren't certain ... feelings ... coming back to the fore.
I like this graphic novel. The art style is fun and loose without feeling lazy, and the characters are remarkably well-rounded. There's maybe a bit too much anxiety and worry suffused through these pages, but that also might just be me, projecting.
It's probably aspirational to think that knowing yourself better – being able to review past decisions, thoughts and feelings from the perspective you had while going through it all – can lead to happiness, or at least a better understanding of your current self. But part of being our best selves requires that we examine how we were in the past, even if only to emulate the things we did correctly (though, honestly, it's more often avoiding making the same mistakes). In that sense, we could all stand to remember why we Hated (Someone) In High School.
Tessa hasn’t spoken to Olive in ten years and she’s not about to start now…readers will delight in this enemies-to-lovers graphic novel with a queer twist: *I Hated You in High School*. Struggling 20-something Tessa has a dead-end job as a barista and the dream of a creative career that never quite seems to take off. When the coffee shop where she works goes out of business, she's able to visit her parents for the first time in years. Arriving at her family home, she discovers that her parents have rented out the basement apartment to her high school nemesis, Olive Virtue. Old wounds resurface during Tessa’s stay, but an accident that traps them in the attic forces them to face their past and think about their future. *I Hated You in High School* is an enemies-to-lovers story inspired by classic romantic movies—with a queer twist. Author and illustrator Kathleen Gros has expanded her short story webcomic into a beautiful tale of love and learning.