I have been thinking about trying this approach. We really need something that's in-between, right? There's going to be code that is boilerplate implementation, and I don't need to drive that - like we have, in the before times, relied on macros and what not to do that work. But then the interesting logic, seeing the suggested implementation, copying or working from that. That's the sweet spot.
I've also been thinking about the partner programming craze phase our industry went through. I write the test, you write the code; well I write the test, LLM satisfies with code. (Then we have less of these weird LLM generated test cases that test _nothing_. We can also use the LLM to suggest tests to complete coverage.)
These would be slower to work this way, but the end result is:
1. humans still learn
2. you have a good grounding in how everything has been written
I've also been thinking about the partner programming craze phase our industry went through. I write the test, you write the code; well I write the test, LLM satisfies with code. (Then we have less of these weird LLM generated test cases that test _nothing_. We can also use the LLM to suggest tests to complete coverage.)
These would be slower to work this way, but the end result is:
1. humans still learn 2. you have a good grounding in how everything has been written