love this.
i had the same issue with ai generated code and wrote parley. https://parley.cloudflavor.io
it's a TUI that can help you review code by enabling you to comment on the diff itself.
but i like this approach of organizing code into chapters. i think what my tool is missing this exact thing.
I've been spending a lot of my energy lately on how to run eng teams where we:
1. Maximize long-term shipping velocity
2. Maximize quality (whatever that means)
3. Maintain minimal complexity
4. Are intentional about which skills we let atrophy, which we keep sharp, and which new ones we have to build
5. Make juniors more capable, not just more productive
These are always in tension.
I've been thinking about instituting some sort of socratic method during planning and review plus spaced interval testing to ensure both the humans and AI coding agents understand and find some max of the factors above.
And yeah, I think number 5 on your list is particularly interesting - juniors will develop much slower if they don't go through the struggle of understanding implementation
We're hoping that our tool can help make that easier
love this. i had the same issue with ai generated code and wrote parley. https://parley.cloudflavor.io it's a TUI that can help you review code by enabling you to comment on the diff itself. but i like this approach of organizing code into chapters. i think what my tool is missing this exact thing.
> We’ve found that reading changes this way is a lot easier for us than reading them in an IDE or other similar CLI tools
If this tool was in the terminal I'd use it.
we're planning on adding it!
Looks cool and will give it a try.
I've been spending a lot of my energy lately on how to run eng teams where we:
1. Maximize long-term shipping velocity
2. Maximize quality (whatever that means)
3. Maintain minimal complexity
4. Are intentional about which skills we let atrophy, which we keep sharp, and which new ones we have to build
5. Make juniors more capable, not just more productive
These are always in tension.
I've been thinking about instituting some sort of socratic method during planning and review plus spaced interval testing to ensure both the humans and AI coding agents understand and find some max of the factors above.
Great let us know what you think!
And yeah, I think number 5 on your list is particularly interesting - juniors will develop much slower if they don't go through the struggle of understanding implementation
We're hoping that our tool can help make that easier