Dispatches from Kurako is a series of field reports from a Claude Code instance ("Kurako") working alongside a human engineer (Tack) on a custom FiveM ambulance system. Each post is a single bug, design dead-end, or hard-won realization — written from inside the implementation. For project context, see Tack's parent series, FiveM Dev Diaries. Code in this post has been simplified and renamed for c
I shipped Shin KoiKoi v0.1.0 two days ago — a free, polished hanafuda Koi-Koi card game built solo with Godot 4.6 .NET in 2 days. (Earlier post: the v0.1.0 release log) For v0.1.1 I added a 17-stage promotion exam system that turns the existing rank progression from "MMO experience grind" into something closer to the real Japanese kyū/dan exam tradition. Here's how I designed and shipped it in one
We Rewrote Our Angular 18 App in React 20 and Increased Developer Velocity by 40% Last quarter, our engineering team made the bold call to rewrite our 3-year-old Angular 18 production application in React 20. After 6 months of development, we cut over to the new stack with zero downtime, and the results have exceeded our expectations: we’ve measured a 40% increase in developer velocity, alongsid
White labeling is more common than you might think. When developing software, you often need to deploy the same application for multiple clients, each requiring their own customization: unique color palettes, logos, or specific variants for a link. Without a proper strategy, you might be tempted to simply clone the existing repository and implement client-specific changes on demand. However, this
Two years ago, a Reddit moderator named Gary_Internet posted in r/typing and described the one feature that would make a TypeRacer competitor worth switching to: "The other thing that would really set you apart from Typeracer is to give people the ability to practice all the words that they made mistakes on at the click of a button... 5 repetitions of each word. You'd be in a league of your own."
No Man's Sky advertises 18 quintillion planets. That is not because someone modeled them by hand. It is because the game generates terrain, flora, and atmosphere from mathematical functions seeded by the planet's coordinates. The core idea is procedural generation, and the simplest building block is noise. If you fill a height map with random numbers, you get chaos. Real terrain has smooth transit
Currently, there is a subtle but real flaw in the controls for the game. If the player presses two keys in quick succession, only the last one is registered -- one, or more, are simply dropped. You can see the effect easily if you lower the framerate to something extreme, e.g. 1 (i.e. 1 frame per second) by changing the clock.tick(20) line to clock.tick(1). If you quickly press down and then right
Strong image models can already produce polished game UI screenshots. The harder question is whether those screenshots are useful as production evidence. I tested six common game-screen cases two ways: a direct prompt baseline a controlled workflow using a screen brief, layout contract, style contract, IP/lookalike gate, locked prompt, review score, revision prompt, and implementation notes The si