Working on an interactive explainer for code. When agents write most of the code, I find I'm losing the working theory of the code/architecture. Code review had typically served a couple of purposes, two of which are catching errors and disseminating codebase knowledge amongst the team. I find that adversarial agent reviews are good at catching errors, and that I prefer to learn about the architecture before/while I'm designing the next feature, rather than after.
I've also been designing a APL/BQN-like language that uses Korean as a way to compact and compose the meanings of the operations.