All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

Why one developer disabled and deleted CoPilot: The productivity paradox of AI coding assistants

By

Bogdanp

8mo ago· 4 min readenOpinion

Summary

The author describes their experience using GitHub CoPilot and JetBrains' local AI completions for IntelliJ over several years. Initially enthusiastic, they ultimately disabled and deleted both tools, finding it improved their productivity and reduced frustration. The article argues that while CoPilot excels at speeding up already-fast monotonous code transformations (like mapping objects to SQL), this benefit is outweighed by drawbacks such as context disruption, over-reliance, and the cognitive cost of verifying AI-generated suggestions.

Key quotes

· 2 pulled
I've come to first disable it and then delete it altogether along with JetBrains' local AI-completions, and generally felt this has been an improvement in productivity and a reduction of frustration.
CoPilot is pretty good at taking things that are already pretty fast, such as monotonous code transformations like mapping an object to a SQL statement, and then making that even faster.
Snippet from the RSS feed
I’ve been using the CoPilot plugin for IntelliJ on and off for the last few years, and while initially pretty enthusiastic, I’ve come to first disable it and then delete it altogether along with JetBrains’ local AI-completions, and generally felt this has

You might also wanna read