It certainly has its limitations. I’ve noticed a few topics where it generally gets things wrong, or I can’t seem to explain it properly. In that case, you may just use it as a reference guide. Maybe toss it some code and ask it what it thinks. It’s not always useful information, but sometimes that leads you down a different road that you would not have thought of before.
Problem is, I only ever need to use something more powerful than a search engine with topics that are too complicated for me and/or not well documented, in which case LLMs fail just as bad. So it’s actually only ever useful to get a general direction of a topic, but even then it could be biased to outdated information (eg. preferring bluetooth.h over DBus based bluetooth handling) or it outright doesn’t know new standards, libraries and styles. And in my experience, problems that have one, well accepted and documented standard don’t need any AI to get knowledge of.
It certainly has its limitations. I’ve noticed a few topics where it generally gets things wrong, or I can’t seem to explain it properly. In that case, you may just use it as a reference guide. Maybe toss it some code and ask it what it thinks. It’s not always useful information, but sometimes that leads you down a different road that you would not have thought of before.
Problem is, I only ever need to use something more powerful than a search engine with topics that are too complicated for me and/or not well documented, in which case LLMs fail just as bad. So it’s actually only ever useful to get a general direction of a topic, but even then it could be biased to outdated information (eg. preferring bluetooth.h over DBus based bluetooth handling) or it outright doesn’t know new standards, libraries and styles. And in my experience, problems that have one, well accepted and documented standard don’t need any AI to get knowledge of.