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
If this tool was in the terminal I'd use it.
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