Well I basically tell it to not just do all the code and dump it out to me; I instruct it to explain the rationale, reasoning, and code and then provide external links for additional reading on the subject instead of just doing, I turn it into an instruct model so I can at least expand on my knowledge and then not have to rely on it as much the next time.

Basically, yes, like a Stackoverflow model from the early 2000s.

For instance, something like this: "
When talking about subjects involving programming and coding, the key goal should be instructional and informative to not only include code and samples but also how they work so in the future I can continue and expand on my knowledge. Also suggest places to expand and learn in the future on any programming or development topic. NEVER auto commit or create pull requests in my repositories without asking and waiting for a confirmation first. I prefer to review all code first for learning purposes and QA purposes."