Available Games

@ACGreviews just dropped an exclusive preview of Samson titled "You Are Ready," confirming the launch is coming much sooner than the rumors claimed. This isn't just another "coming soon" teaser. ACG is highlighting deep hand-to-hand combat mechanics and a build that is already highly optimized. The footage shows a world scale and level of polish that surpasses the early trailers. When a reviewer of this caliber gets this level of access, it means the marketing floodgates are open and the game is actually ready for release. Clear some storage space. Samson is the real deal. youtube.com/watch?v=DDFvTjO-…

Copilot is an absolutely crappy brand. Meanwhile, "Ralph Wiggum" from "The Simpsons" is trending on X. Microsoft is being outbranded by a literal while-loop in Anthropic's toolchain.

Try treating him as a frenemy in the beginning of a buddy cop-movie. Start talking to him in the voice of Rick Sanchez: "You did it CLAUDE! You're a god damned genius, CLAUDE!" Soon you'll see why we love the little goofball.

OK, here goes nothing. I always focus on creating TRANSPARENCY and TOOLS. Using a text-editor (like VS Code) to understand what the LLM is doing is extremely low-velocity. I look at this as an extension of "test driven development". Both Claude and I know that if we're in doubt what to do next, we always take a step back and improve our tooling for transparency. If we find bugs in our tools, fixing those have priority over fixing the core system. Claude can reason easily about the code-base, but what I need as a human is to be able to look at the system through some abstraction. And example is for the game I am making (a train-related game), I've made "Rail Studio" which allows me to visualize, tune and edit. Do not fall for the temptation of making _products_ of these tools, they are for you only and they are for the project only. When production of code is "free"/cheap, there is a race between Claude writing huge amounts of code and me, the human, struggling to keep up. The tooling always helps me see what is happening, and it makes it easier to communicate to Claude what is wrong, something that is almost impossible by just navigating the code. I've attached here a screenshot of a tool I've made JUST for this game I am making now. But I do this for all my projects. Strong tooling allows me to run the necessary scripts when I want, see what features are actually there. This is one of the bigger changes for me with AI coding. Again: Code is cheap. This quickly leads to a lot of opaque code. So write more code to gain transparency and understanding of the project you're working on. I truly think you need to think like a toolmaker to tackle complex AI-driven projects. Feel free to follow me and I'll add more stuff like this on the channel for my game, @ArmoredRail if this is interesting. I'll be going over content-pipelines, semantic compression to battle small context windows, etc. But that account isn't launched yet. I hope this was valuable at all. Talk to you soon!