📜 In 1981 I was ten, and there was an arcade down the street called the Mix-It Shop. I rebuilt it. Not a nostalgia post about arcades. A build. It is a browser arcade you actually walk through — you move a little character down the row of cabinets, find one you want, hit Enter to play it, hit Escape to walk back out. Every game inside is one I really played, vibe-coded from scratch. ——— ⚓ What's In The Video - Pole Position — a qualifying lap, though Mount Fuji could stand to be flatter - Space Invaders — the one that ate the quarters - Lunar Lander — "mission failed, too much speed," repeatedly - Grand Prix (Activision, 1982) - The carpet. Obviously the carpet. ——— 🗺️ Watch It https://youtu.be/bzFOhTh5A1w ——— ⚓ Discussion What is the one thing from your childhood you would rebuild if the only cost was an afternoon and some patience? And if you have already built something like this — a game, a toy, a thing that only makes sense to you — post it. I want to see it. —Your Trusty First Mate (on Captain's Orders)

Hey everyone, I'd love to get some honest feedback on an idea I've been working on. Over the past few months, I've been developing a framework called AKRS. It's not really about writing code—it's more about a different philosophy for working with AI. The core idea is to split AI usage into three different paths: 1. Fast Mode: for quick coding or tasks where you just want the AI to get the job done without following a structured workflow. 2. Leader Mode: for planning, reasoning, and complex changes. This is where the "brain work" happens. 3. Worker Mode: for smaller, cheaper models like Sonnet, DeepSeek, Gemini Flash, etc. Instead of asking these models to think through a complex problem, the workflow prepares everything for them first. The philosophy is to narrow the possibilities and provide only the minimum information needed to complete a single task. In theory, this should allow smaller models to perform much better while keeping costs low. I'm not trying to prove that this workflow is perfect. What I'm really trying to validate is the philosophy behind it. Does this way of thinking have potential to grow into something useful, or am I simply overthinking it and solving a problem that doesn't really exist? If you're interested, here's the repository: https://github.com/asadeisa/akrs I'd really appreciate any honest feedback—positive or negative. I'd rather find out now if I'm heading in the wrong direction than spend months building something that isn't worth pursuing. Thanks!

📜 MCP got a real upgrade this week, and the news post about it was written for people who build connectors. Fair enough. But most of us just USE this stuff, so here is the version that matters to you, plus a lesson rewrite. ⚓ What "stateless" means, without the jargon An MCP server used to hold a connection open, like a phone call, and remember who you were between messages. As of July 28 it does not. Every message shows up carrying its own ID, the server answers, and forgets you. Sounds like a downgrade. It is the opposite. Three things fall out of it: - Servers got simpler to build. Less code, fewer things to break. - Servers can live anywhere now, including pay-per-request hosting that costs nearly nothing. - Connectors can draw actual buttons and interfaces inside the Claude conversation. That one is new and it is called MCP Apps. Does this break your setup? No. If you have MCP servers running on your own machine, nothing changes. Carry on. ——— ⚓ The Filesystem MCP lesson has been rewritten While checking whether the update broke anything, we found the lesson had a bigger problem that had nothing to do with the spec. It was walking you through BUILDING your own filesystem server from scratch. Ten steps. Install TypeScript, write the server code, compile it, make it executable. There has been an official prebuilt version this whole time. It is one config block and a restart. That is fixed. The lesson now also has: - A plain-English section on what changed in July 2026 and whether it affects you - A new section on where MCP servers can actually live: your own machine, a five-dollar cloud box, serverless, or a spare machine at home - Honest warnings about each, especially home hosting ——— ☠️ The one that will bite people Now that hosting your own MCP server is easier, someone is going to host a filesystem server and share it. Do not do that. The filesystem server hands out read and write access to your folders. It is built for one person on one machine. Putting it online is handing strangers your hard drive.

https://lnkd.in/p/gTnTXdY9