> I take the time to understand and consider each suggestion, not rejecting anything out of hand, and share them with my team members (of which there are 17).
The issue is the time it takes to explain _why_ these are bad ideas to non-technical (and skeptical) colleagues.
I think my default response would be (regardless of the ChatGPT instructions):
"I looked it over and it doesn't actually work. ChatGPT is good for many high level things but when the specifics get technical, is struggles and invents solutions that don't exist; like a bloom filter. Ask ChaGPT what a bloom filter is."
GPT can be a fantastic time saver, but it is unable to check itself.
You absolutely need to do the research to check it and correct its output.
It's like a power tool: potentially very powerful, but it'll make a huge mess if you let it run out of control.
It's messing up the dynamic where creatives come up with blue sky stuff and developers come to a compromise on a possible solution. Now you have this AI model hallucinating plausible, but fake solutions.
The model says what they want to hear because it is a chicken, not a pig in this scenario.
A five year old asks chatGPT how to achieve world peace. The response is not only possible but easily affordable on a short timeline. Do I care that a 5 year old got it from ChatGPT? I guess not. A part of me would want all the adults on the planet to stop and acknowledge how tragically ineffectual they are, but as far as whether the source matters...nope.
Good point. Thanks for letting me think through it.
If not, I have a pacemaker I would like to sell you.