1. In our codebase, we leave links to the stackoverflows as documentation if it's something that someone else may question. Exact same concept just with ChatGPT.
2. I'm working with the Salesforce API which has been absolutely tedious to use but chatGPT, while not great at everything, has been giving awesome results back that otherwise would take me hours to hunt down. Sometimes responses get a lot of information back with multiple code blocks that I'm then unable to copy paste over & I'd rather send the conversation than spend 15 minutes typing back & forth explaining myself to a co-worker.
I completely understand you may not have a use for this but I think there could be awesome use-cases for it nonetheless for other engineers.
1. In our codebase, we leave links to the stackoverflows as documentation if it's something that someone else may question. Exact same concept just with ChatGPT.
2. I'm working with the Salesforce API which has been absolutely tedious to use but chatGPT, while not great at everything, has been giving awesome results back that otherwise would take me hours to hunt down. Sometimes responses get a lot of information back with multiple code blocks that I'm then unable to copy paste over & I'd rather send the conversation than spend 15 minutes typing back & forth explaining myself to a co-worker.
I completely understand you may not have a use for this but I think there could be awesome use-cases for it nonetheless for other engineers.