I would urge caution for using it. I already see too many of my juniors starting to rely on it.

The problem (when it works perfectly - and it doesn't all the time), is that you don't learn anything from using it. You aren't learning why it's picking the way to write a specific piece of code. You can ask it to explain it, but you have to go out of your way to do that in standard gpt, in vscode it won't. This is incredibly important when trying to get code to fit within an organization or team's code, where there are already standard patterns, worries about things like runtime, or scalability. You need to understand line by line what that code is doing.

So, I won't say don't use it, but don't depend on it. Learn why it made the choice it did, and dig deeper into the ramifications. Ask it for alternatives and why it chose that one. Ask it for runtime information, how it performs at scale, if it's concurrent and thread safe, anything you can. I use it to help me think outside the box, and it's great at that, but I wouldn't want an engineer working for me who didn't understand what the code was doing.