Like any tool, really depends on how you approach using them.
Giving it a problem statement and just blindly asking it for an answer will always yield the worst result, but I find this is often our first instinct.
Working with it to solve the problem in a "step-by-step" manner obviously yields a much better result as you tend to understand how it got to the answer.
I look at it as similar to rote-memorization vs. learning/understanding.
Most often I now use it to help find the "right question" for me to ask when starting with a new topic or domain or synthesize docs that were difficult for me to understand into simpler or more digestible terms.
Giving it a problem statement and just blindly asking it for an answer will always yield the worst result, but I find this is often our first instinct.
Working with it to solve the problem in a "step-by-step" manner obviously yields a much better result as you tend to understand how it got to the answer.
I look at it as similar to rote-memorization vs. learning/understanding.
Most often I now use it to help find the "right question" for me to ask when starting with a new topic or domain or synthesize docs that were difficult for me to understand into simpler or more digestible terms.