AI should not be in Code Editors

Badr chanaa — Sat, 10 Jan 2026 08:39:39 +0000

AI has become, over the last few years, an impossible technology to ignore. Almost everyone ignored it at some point, and now most developers have adopted it for daily use—both professionally and personally—including myself.
However, AI is not meant for code editors. It should stay in the browser.

Coding requires deep thinking about every line while maintaining the overall structure and design of the system. The AI we have today cannot do this consistently or deeply (and no, this is not a prompt issue). When embedded directly into the editor, it mainly helps with small, repetitive tasks while overlooking the broader architecture of the project.

Yes, it can reduce typing time, and for less experienced developers it may even produce better-looking code than they could write themselves. But it can—and will—introduce subtle bugs. This creates a tradeoff between speed and code quality and security.

So should we still include AI in code editors because it saves time? No. And here’s why.

First, typing speed is almost never the bottleneck in software development. Second, the time saved by AI is often lost debugging subtle issues introduced by generated code and overlooked by the developer.

For less experienced/skilled developers (and sometimes even experienced/skilled ones, aka the x10 devs), AI can generate new ideas or better implementations. However, as a project grows, the developer may lose track of what is actually happening because they do not deeply understand the generated code. This leads to even more time spent asking the AI to explain the code, searching documentation, and filling gaps in knowledge about algorithms, libraries, or techniques they never truly learned.

While that learning process is not wasted—and can improve the developer’s skills—it does not require AI to be embedded in the editor. All of this can (and should) happen in the browser.

Another reason AI should not be in code editors is that it encourages laziness over time. Even experienced developers risk skill atrophy. Gradually, they may become similar to less experienced developers: relying on AI for things they once knew, then wasting time debugging AI-generated bugs they failed to notice.

In the future, AI may or may not become capable of reliably writing large, complex systems. If that happens, we may not even need code editors—only interfaces to observe and validate the output.
Until then: no AI in your code editor.

Note 2: This post was reviewed and rewritten by an AI—in the browser.
Note 3: Sorry ${PREFERRED_AI_EDITOR}

DEV Community: Badr chanaa

AI should not be in Code Editors