I find it's great for very generic work, like boilerplate or where you have forgotten how to implement a specific single, well defined algorithm. However, relying on its output is very risky if you aren't verifying everything it puts out. A good test to show this is to ask it to write a short essay on something you know very well, then behold all the incorrect information it enthusiastically tries to feed you.
Also:
* It has a horrible habit of inventing properties on objects or methods in libraries.
* It will very happily straight up lie to you about things it does
* Often when you ask it to make a specific change, it will give you back exactly the same as last time.
* For the love of God, don't put any company-owned code into it.
Love that channel and the message that with a small amount of effort and skill you can make excellent dishes 1000% better (and probably healthier) than the pre-packaged version. You don't need the most expensive cuts, or a home made demi-glace, just solid fundamentals with common ingredients.
Also:
* It has a horrible habit of inventing properties on objects or methods in libraries.
* It will very happily straight up lie to you about things it does
* Often when you ask it to make a specific change, it will give you back exactly the same as last time.
* For the love of God, don't put any company-owned code into it.
* Maybe I'm just bad at prompting...