We surveyed 730 coders and developers about how (and how often) they use AI chatbots on the job. The results amazed and surprised us, capturing an industry at fundamental odds with itself.
Here's a deeper look:
https://www.wired.com/story/how-software-engineers-coders-actually-use-ai/
Here's a deeper look:
https://www.wired.com/story/how-software-engineers-coders-actually-use-ai/
Comments
As a developer, there are many levels to this. I do find value in using Cursor's autocomplete features. Asking AI for help when I'm stuck is usually worse than using Google. Full on "vibe coding" isn't viable for medium to large projects (for now?).
You're fucking assholes, most of you. Shove all those pop up adds up your ass.
Here are how some other stats line up:
https://www.wired.com/story/how-software-engineers-coders-actually-use-ai/
https://www.wired.com/story/how-software-engineers-coders-actually-use-ai/
To see how software engineers are using AI, take a look at the full breakdown here: https://www.wired.com/story/how-software-engineers-coders-actually-use-ai/
It winds up being faster for me to just find a real sample written by a human every single time.
When you get to doing interesting and novel things it's nearly useless. Which makes sense given how they're trained.
Unfortunately all the middle managers THINK it’s neat and keep trying to “help” by putting useless code samples in front of me, so it’s actually a significant time sink even though I’m not personally using it.
In the time I toyed with it because work was pushing for us to use AI assist, it was just constantly wrong. I spent more time teaching the stupid thing than anything else.
"Upper management does not understand what AI is and thinks it will solve untold problems. Junior devs rely on it too much without understanding their code first."