zlacker

>>martin+(OP)
I'd argue 2 types of users are

* People using it as a tool, aware of its limitations and treating it basically as intern/boring task executor (whether its some code boilerplate, or pooping out/shortening some corporate email), or as tool to give themselves summary of topic they can then bite into deeper.

* People outsourcing thinking and entire skillset to it - they usually have very little clue in the topic, are interested only in results, and are not interested in knowing more about the topic or honing their skills in the topic

The second group is one that thinks talking to a chatbot will replace senior developer

>>Punchy+xO
You can get it to type for you. I don't really type the code myself anymore. I review it and then have it make corrections. Very rarely I will jump in and type and probably should more because the token cost, but it's novel that I can make it change the code exactly how I want, so I do that instead.

It's nice to brainstorm with too, but you have to know what you're doing.

It gets stuck on certain things for sure. But all in all it's a great productivity tool. I treat it like an advanced auto complete. That's basically how people need to treat it. You have to spend a lot of time setting up context and detailing what you want.

So does it save time? Yea, it can. It may not in every task, but it can. It's simply another way of coding. It's a great assistant, but it's not replacing a person.