I have this crazy idea in mind that goes something like this, in a single keystroke:
- Assemble a program in the classic uxn self-modification style
- Run tests that records "fitness" in the routine's literals and iterator boundaries
- Save the modified image
- Disassemble it and keep working
@neauoire So one thing about evolutionarily evolving "programs" is that code tends to have a "rough" fitness landscape, so that the shortest-(hamming/edit)-distance path between two fit points may be mostly unfit or mostly nonfunctional. My conclusion working with this sort of thing only works well when the shape of the fitness landscape can be made smooth. Then again, if the peturbation is being done by a human mind instead of an algorithm, maybe you actually *can* find good outcomes that way