I've been a software engineer for decades and I still use it daily for that purpose. It's like having superpowers. Even if I know how to do something, sometim

I've been a software engineer for decades and I still use it daily for that purpose. It's like having superpowers. Even if I know how to do something, sometimes explaining it is easier than writing out all of the code. An example recently would be in a TypeScript project when a class-based approach to something was deprecated, in favor of a functional approach. I only had to paste the old function signature and say "convert this to an arrow function". That already is less typing, but after that I was able to paste the other examples and say "do the same with this" and they were all correctly quickly converted. Was it easy to do myself? Yes. Was it faster to do myself? No. Or, I may not know how to do something. In a toy desktop project I had in C#, I wanted an image to fade to greyscale and then fade out. That, I had no idea how to do. So I simply told it that, and added "optimized for performance", and it gave me a function including a hard-coded object that instantiated an array of arrays with certain values. Where did ".3f, .59f, .11f" come from? I don't know, and that point I didn't care, because the whole thing worked perfectly on the first try. In this case, a project for myself, only the result mattered. I did go read the documentation later to see why that works, just out of curiosity. Plus, it explained it ... and was right. Obviously I review the code and am careful what I send it, but if it's going to shave minutes off my day every time I use it, this stuff adds up.