Not really, it’s been pretty useless for me. But I’m also a very senior developer, I’ve been coding for 18 years so more often than not I’m stuck on a problem much bigger than the best AI can possibly handle, just in amount of context needed to find out what’s wrong.

It’s still much faster for me to just write the code than to explain what I want to an AI. IDE snippets and completion just makes it super quick. Writing out code is not a bottleneck for me, if anything I shit out code and shell commands without a thought. It comes out like it’s regular speech.

I’m also at a point where I Google things out, and end up answering myself 5 years ago, or asking 5 years ago and there’s still zero answers to the question.

I do see my juniors using Copilot a good bit though.

AI chatbots are sometimes quicker than using official library documentation. I daresay usually quicker, for anything but documentation that I know really well already.

I haven’t spent my own money on a development tool in a long time, but I find it worth a few of my employer’s dollars.

It’s hardly life-changing, but it’s convenient.

I can’t comment on it’s mistakes or hallucinations, because I am a godlike veteran programmer - I can exit Vim - and so I - so far - have immediately recognized when the AI is off track, and have been able to trivially guide it back toward the solution I’m looking for.

The chatbot version? Meh, sometimes, but I don’t use it often.

The IDE integrated autocompletion?

I’ll stab the MFer that tries to take that away.

So much time saved for things that used to just be the boring busywork parts of coding.

And while it doesn’t happen often, the times it preempts my own thinking for what to do next is magic feeling.

I often use the productivity hack of leaving a comment for what I’m doing next when I start my next day, and it’s very cool when I sit down to start work and see a completion that’s 80% there. Much faster to get back into the flow.

I will note that I use it in a mature codebase, so it matches my own style and conventions. I haven’t really used it in fresh projects.

Also AMAZING when working with popular APIs or libraries I’m adding in for the first time.

Edit: I should also note that I have over a decade of experience, so when it gets things wrong it’s fairly obvious and easily fixed. I can’t speak to how useful or harmful it would be as a junior dev. I will say that sometimes when it is wrong it’s because it is trying to follow a more standard form of a naming convention in my code vs an exception, and I have even ended up with some productive refractors prompted by its mistakes.

Depends on if you want to work with existing code. LLMs tend to be good at generating small code snippets but not good at understanding / finding errors in existing code