• 2 Posts
  • 46 Comments
Joined 3 years ago
cake
Cake day: July 13th, 2023

help-circle


  • LLMs are okay at writing code, but not good at software architecture

    This is very much the case. I have a local LLM that does a fairly good job of writing code for quick and easy apps that I might need - for instance, last week I wanted to create a simple floor plan of my house and couldn’t find exactly what I wanted online, so I had my machine create a web based app to do it. But, when I tried to use it to create a fairly large and complex text based adventure game when it reached a certain size my LLM just couldn’t handle it any longer. That project stalled for a bit until a couple of weeks ago when Fable 5 was released… as a test I pointed Fable at that code base and in about 45 minutes it had completed the entire game engine.

    I really don’t like the idea of corporate owned LLMs, but I am very impressed with Fable and can’t wait until the Local LLM community is able to replicate its functionality.



  • Last night I decided to try Little-Coder to work on a game that I’ve had in the ‘plannng’ phase for a while. I had a few issues getting Little-Coder to work with my system, but once it was working I pointed it to the project fact sheet in my Obsidian vault and told it to get familiar with the project and ask any questions. It had a few questions and then wanted to know if I wanted it to get started on a prototype for the gameplay. The game is a narrative driven politics game and I asked it to create the prototype as a brower game. It ran for about 40 minutes and then had the working prototype. There were a couple of bugs with some buttons not working, but those were easy to fix.

    This is really impressive. I’m making this game for my daughter and I let her play the prototype (which is very repetitive at this point since the ‘narrative’ hasn’t really been written yet) and she loved it. She played it for about 15 minutes before realizing that it had started repeating. I’ve been working on the game all day today and she came in a bit ago and asked when she can play again.

    And thanks for that video on Qwen3.6 27 dense… I might have to throw my system at it and see how it handles things.


  • I did some analysis on OpenCode, Little Coder, Aider, OpenClaude and ClawCode and each one had potential issues with my specific setup (OpenCode and OpenClaude have a looping bug at the moment, Little Coder is brand new and has potential, but I’m leary of new projects, Aider is promising but had some unknowns)… anyway, as I was evaluating these I realized that I currently use Claude Code, all I have to do is use that with my model rather than using their models. A few quick changes and now I have Qwen3.6 in Claude Code. I asked it to create a web-based Tetris game… 7m13s later I have a fully functional, minimally buggy Tetris game in my browser!





  • I hadn’t heard of OcuLink before the Framework event yesterday… and now I’m intrigued. How does that connect to the Framework Desktop?

    And as far as tools go, I tend to borrow ideas from others and then build them specific for my setup. For instance, a few months ago I came across a project called OpenBrain that uses a vector database for memory storage and retrieval. I leaned on Claude and asked it to evaluate the OpenBrain project and to let me know how we could use the concepts for my local system. Claude chugged away and then gave me its recommendations, which included spinning up PostgreSQL, creating an ‘Observer’ to watch my OpenClaw and Claude sessions to pull memories into the database, setting up an embedding LLM server to generate the embeddings, and then a process that runs nightly to remove duplicate memories, combine similar memories and archive old memories. If I recall almost all of these were components of OpenBrain, but I’m cautious about using other people’s code and appreciate that Claude is a good tool for using ideas from other projects without actually needing to use the whole project itself.

    One instance recently where I’m glad I did this was Milla Jovovich’s MemPalace… since I already had a memory system in place I didn’t need to use her project, but one thing I did find very intriguing was the AAAK, which she had described as a lossless compression language for AI agents. I asked Claude to evaluate all of MemPalace and see if there was anything that would be an improvement to my setup, and Claude also got excited about AAAK. Claude said that everything else we were doing was as good or better than MemPalace, but if we could add an AAAK version of each memory that would help lower the token usage (but we kept the full prose memory to help with search). We implemented it and I asked Claude to pull some random memories from the db… and it was immediately clear that there was no way AAAK was lossless because a lot of my memories had to do with system details, including IP addresses, and the AAAK didn’t include any IP addresses. Of the 1800 memories that I had stored, Claude was only able to find 3 where enough meaning had been preserved with AAAK to be usable. It was easy to remove from my system - and I just checked and the project no longer refers to AAAK as lossless.

    Using this method I also built a filesystem based context system that allows any LLM on my system to use the same skills, context, agents, projects, and memories (although the memory folder just has instructions on how to access the memory database). This was another project I saw from someone else and I used a lot of their ideas, but tweaked things to fit my needs.

    Other tools where I am using other’s projects are ‘Faster-Whisper’ for speech-to-text, ‘Piper TTS’ for text-to-speech, ‘Moondream2’ for image analysis and QMD Search for indexing my Obsidian Vault and putting it into the memory system.










  • Great points, and there’s some amazing discussions going on here!

    One thing I’d like to add is EVERYONE needs to start setting up some meshtastic nodes. It’s really easy to setup (just hook up a USB cable from your computer to a esp32 board, visit a website to get the configuration, and that’s pretty much it), it’s cheap (as little as $30) and it is secure. Build 2 nodes (one to leave at home, and another for your backpack). This way you’ll be able to communicate should the Internet become unavailable or unsafe. You can also use this at a protest so that you still have a means of communication without needing to bring your phone that the Feds will be able to track.