Les Orchard <me@lmorchard.com>

This post grew far beyond my original idea, but I wanted to set out my thoughts on building a custom engine before delving into the technology itself. Building an engine takes time, but it gives us control over how the game loads and updates, removes engine-licence fees, and teaches us about asset compilation, rendering, and optimisation. We can even expose parts of the engine to players, allowing them to improve the game or create mods (and potentially entirely new games) with our technology. After Unity’s runtime-fee announcement, technological independence became an even more important concern for game developers.

SwitchNOW is a native Nintendo Switch homebrew client for GeForce NOW. It is distributed as an .nro and combines a controller-first Borealis launcher with native WebRTC signaling, H.264 video, Opus audio and low-latency input delivery.

About an hour later, once it became clear to me that the web app I had launched using Claude was strikingly similar to his open source project, even reproducing a bug he had later fixed, it was clear that there wasn’t anything to do except to redirect the domain directly to him and kill any plans I had to launch an iOS app for the project.

Persona 5 Royal was 80% off on Steam recently and as I already established, I will repeatedly pay Atlus for their games. Only problem is I don't want to start a full play through yet again. Thankfully we have adversarial interoperability.

In short, the parts of my old archived posts that survived 14 years were the ones I owned and kept simple; the parts that broke were the ones I outsourced to someone else's server.

I totally get the pressure to produce. Academics have been long turned into content churners. ‘Publish or perish’ in some regions and institutions meant how much could you produce in how little a time. As a postgraduate student I attended a workshop where a senior professor describes turning the same conference paper into five publications FIVE!? Who do they think was going to read all this samey shit?

Writing students once learned that putting the most important information first in an article was the preferred, humane way of reporting on a situation. This allowed readers to quickly decide if a story interested them without having to read further.

Use when you want to know what shape a developer or user reaches for when they first meet your API, config format, CLI, or UI, so you can make your design that shape. Spawns a blind agent that commits the design it EXPECTS before seeing the real thing, then reports the shape they reached for and conform-first recommendations (make the API whatever the guess is). Triggers on "is this intuitive", "would a developer guess this", "intuition probe", "blind-test this API/config/CLI", "test the DX/UX of", "what would someone expect here", "make the API whatever the LLM guesses".

So the literal shape of “itadakimasu” is not “thank you.” It is closer to: “I humbly receive.” And the thing being received is the food. Not the labor of the cook — that has its own phrase, said afterward, to the person. “Itadakimasu,” said before, with the eyes on the plate, is addressed downward and outward, to what is about to become part of you.

Here is a collection of screenshots (obfuscated) of dozens and dozens of online comments from many platforms (Reddit, YouTube, Instagram, Facebook) containing accusations or confusion that my artworks and comics are AI-generated. Despite creating every piece by hand, despite sharing timelapses, the comments keep coming, and they're getting stronger.

6 months after Cloudflare acquired the team behind Astro, co-founder Fred Schott explains how an AI agent is emptying the project's issue tracker -- and why the hardest part is still left to a human