[DanielHB]

I mostly used it for exploratory analysis of tools/libraries I am not familiar with, where it points me the parts of the API docs I need to lookup to verify the output. Then I manually adapt or rewrite it.

So in the end I use it fairly often when setting up new things (new infra, new files, new tools, new functions, etc). Although the time it saves is not coding time, but googling/boilerplating time. But in practice I work in a well established project where I rarely do this kind of thing (I don't think I even created a new file in the project last week).

If I am already familiar with the tool/library I almost always skip it (occasionally autocomplete is useful, but I could easily live without it). Occasionally I used for small self-contained snippets of code (usually no more than a single function). Last one I remember was some date formatting code.

[skydhash]

Some project do have nice documentation that is a pleasure to use. Laravel's documentation, Postgres'one,... Even if I can get an answer faster with google search and now LLMs, I just open the main documentation site and spend an extra 5 minutes looking around.

[DanielHB]

I mean it more points me about stuff I don't know that I don't know.

For example, I use it quite a lot when setting up new terraform configuration on resources I am not super familiar with, it often points me out to resources and options I didn't know existed. Of course I always look up everything it spits out (it pretty much never outputs something that actually runs anyway and even when it does it doesn't work out of the bat).

But once the thing is set up, it is almost useless to use it to make small changes.

[skydhash]

Maybe I lack a sense of rush, but I usually take the slow lane for these kind of work. Actually reading through the whole documentation and taking notes. Maybe do some experiment. I'm wary of things going wrong and me not being able to give a clear and short explanation on the cause. If something is important for me to do, I may as well do it well (or explain the tradeoffs that makes it a hacky solution instead).

[jimbokun]

It can be hard to explain to people that slowing down to make sure something is done right, can make the overall project go much faster.