we use Claude at work so i decided to let it take a crack at genoQs code.
it worked!
so after years of wanting to make a few changes like adding the flow shapes from NEMO and incorporating a better chord mode, and bringing back some older features we are now here. i will share the actual elf and code once i have time to make sure more bugs have been ironed out. right now all these features run and dont crash, there are a few small things i have to fix with LEDs either being lit or not lit.
here is a pdf explaining all the new features
Very cool! I've been thinking about doing the same thing to fix the timing issue in my feature branch. The codebase is small enough for the AI to generate context `.md` files about the code and use that to make just about any change within minutes. I'd feed the AI the manual, then tell it to create a plan to run across several sessions to generate the context files with a root context. Then when you want it to do something just load the root context file and it will load whatever else it needs, context, code.
Maybe ask it to write an emulator harness with unit tests for every feature/capability. Then ask it to rewrite all of the code in Rust. Then ask it to write a VST UI to use it as a direct MIDI controller in a DAW for high resolution and zero latency grid recording... The ideas keep coming.
@eellis this is exactly what i did. i loaded everything i could find on genoqs including the forum and any pdf into my claude workspace and taught it all about the machines by many q and a sessions as well as giving it context for how the code and the documentation differ/work together.
its wild how much you can get done with all this. i was creating multiple features per day with very few bugs (mostly just LED stuff), it was wild
