Claude Code killed my need for an IDE—and I’m not going back


IDEs, or integrated development environments, have long been a staple of the development world. I’ve used one for decades. However, switching to Claude Code completely changed the tools I use for development, and I’ve simply left IDEs in the dust.

I used to hand-code everything in an IDE

Terminal text editors worked but lacked a lot of features that IDEs brought to the table

Concept of computer programming or developing software. Laptop computer with code on screen. Heart, message, cog, home, user, cloud, and lock icons. Credit: Coralnes / Shutterstock

If we rewind time about 15 years, I was just getting started with development by building applications for the Palm webOS platform. Then, I moved to building apps for Windows Phone 7, and eventually I was building full Android ROMs. Most of my development was done within an IDE because they were simply the best tools at the time.

Some programming I did do through VIM because I was doing it on a remote server, but, if I could, I would simply use an IDE because of the text completion, syntax highlighting, and the fact that I was used to using a proper text editor instead of a terminal.

My IDE of choice was either IntelliJ or a more simpler system that was basically a supercharged text editor, Submlime Text 2. One of the main reasons that I preferred to work within an IDE was autocomplete, tab complete, syntax highlighting, and, most importantly, bracket highlighting.

I can’t tell you how many times I would miss a closing bracket or comma, only for the IDE I was working inside of to point it out. It was crucial for me whenever I was hand-writing code—it was just a way of life.

My introduction to agentic coding was still within an IDE

It was clunky but it worked

As 2025 came to a close, I tried vibe coding for the first time. My introduction to this methodology of writing code was, yet again, within an IDE—Antigravity. I utilized Antigravity because it was included with a plan I was already paying Google for and allowed me to enjoy agentic coding without another subscription.

Prior to my use of Antigravity, I did have VS Code downloaded on my computer if I needed to just edit a simple text file here or there, but I never really used it heavily. Antigravity, on the other hand, was my lifeline once I started using it.

Person typing on the OnePlus Keyboard 81 Pro with rainbow backlighting.


Why I’m learning to code in the age of vibe coding

I’m not giving in to the vibes yet.

I found it nice to be able to build apps using AI and have a full IDE next to me so I could check the code, make modifications, and dive deeper into what the AI was putting out. This was crucial in the early time of me vibe coding, but it was definitely clunky.

Antigravity is based on VS Code, so the experience is quite similar. The problem is, as time went on, I was editing code less and less, and prompting more and more.

AI coding definitely isn’t perfect, but it has gotten much better over the several months that I have been using it. I still need to review code sometimes, and I’ll have to edit a file here or there, but that’s becoming the exception, rather than the rule. Because of that, I simply don’t need a full IDE anymore.

Claude Code’s TUI experience means I just live in the terminal now

Nano is my friend

An iPad Pro running Claude Code in a Terminus window with Threads open. Credit: Patrick Campanale / How-To Geek

Since moving from Antigravity to Claude Code, I have fully moved away from using an IDE period. I use Claude Code to do 99% of my work now, and then, if I need to edit a file, I simply open a new terminal window and use nano to edit the file.

I’ve become well versed with nano through the use of my Linux servers, as it’s often more simple to use nano over SSH than it is to mount the server to my computer, open the file up in a text editor, and edit it that way. This has definitely prepared me for Claude Code.

When I was using Codex for a bit through the Codex desktop app, I was still using this same approach—AI agent writes the code, I use nano and cat to check the files as needed. Ditching the IDE has greatly reduced the workload my Mac has to handle as terminal-based tools are lighter weight on the operating system.

In fact, I’ve found that I can edit individual files much faster through nano in the terminal then I could when I was in my full IDE. The terminal is simply my development home now, and I’d have it no other way.


IDEs still have their place, just not in my development workflow

There are definitely still reasons to use IDEs even in 2026, I just no longer have one. Given how well Claude Code and Codex work for my programming needs, I’m modifying files by hand less and less, so a full-fledged IDE is just overkill for me.



Source link

Leave a Reply

Subscribe to Our Newsletter

Get our latest articles delivered straight to your inbox. No spam, we promise.

Recent Reviews


The Samsung Keyboard supports glide typing, voice dictation, multiple languages, and deep customization through Good Lock. On paper, it’s a very capable and perfectly functional keyboard. However, it’s only when I started using it that I realized great features don’t necessarily translate to a great user experience. Here’s every problem I faced with the Samsung Keyboard, and why I’m permanently sticking with Gboard as my main Android keyboard.

I have been using Gboard and the Samsung Keyboard on a recently bought Galaxy S24, which I got at a massive discount.

Google’s voice typing doesn’t cut me off mid-sentence

Fewer corrections, fewer cutoffs, faster dictation

I might be a professional writer, but I hate typing—whether it’s on a physical keyboard or a virtual one. I type slower than I think, which I suspect is true for most people. That becomes a problem when I have multiple ideas in my head and need to get them down fast. It’s happened far too often: I start typing one idea and forget the other. Since jacking my brain into a computer isn’t an option (yet), I’ve been leaning more and more on voice typing as the fastest way to capture my thoughts.

Now, both Samsung Keyboard and Gboard support voice typing, but I’ve noticed that Gboard with Google’s voice engine is just better at transcription accuracy. It picks up on accents flawlessly and manages to output the right words. In my experience, it also seems to have a more up-to-date dictionary. When I mention a proper noun—something recently trending like a video game or a movie name—Samsung’s voice typing fails to catch it, but Google nails it.

That said, you can choose Google as your preferred voice typing engine inside Samsung Keyboard, but it’s a buggy experience. I’ve noticed that the transcription gets cut off while I’m in the middle of talking—even when I haven’t taken a long pause. This can be a real problem when I’m transcribing hands-free.

Gboard offers a more accurate glide typing experience

Google accurately maps my swipe gestures to the right words

Voice typing isn’t always possible, especially when you’re in a crowded place and want to be respectful (or secretive). At times like these, I settle for glide (or swipe) typing. It’s generally much faster than tapping on the keyboard—provided the prediction engine maps your gestures to the right word. If it doesn’t, you have to delete that word, draw that gesture again, or worse—type it out manually.

Now, both Samsung Keyboard and Gboard support glide typing, but I’ve noticed Gboard is far more accurate. That said, when I researched this online, I found a 50-50 divide—some people say Gboard is more accurate, others say Samsung is. I do have a theory on why this happens.

Before my Galaxy S24, I used a Pixel 6a, before that a Xiaomi, and before that a Nokia 6.1 Plus. All of my past smartphones came with Gboard by default. I believe Gboard learned my typing patterns over time—what word correlates to what gesture, which corrections I accept, and which ones I reject. After a decade of building up that prediction model, Gboard knows what I mean when my thumb traces a particular shape. Samsung Keyboard, on the other hand, is starting from zero on this Galaxy S24—leading to all the prediction errors. At least that’s my working theory.

There’s also the argument for muscle memory. While glide typing, you need to hit all the correct keycaps for the prediction engine to work. If you’re even off by a slight amount, the prediction model might think you meant to hit “S” instead of “W.” Now, because of my years of typing on Gboard, it’s likely that my muscle memory is optimized for its specific layout and has trouble adapting to Samsung’s.

Swiping vs typing.


Is Swiping Really Faster Than Typing on a Phone Keyboard?

Which typing method reigns supreme?

I mix three languages in one message, and Gboard just gets it

Predictive multilingual typing doesn’t get any better than this

I’m trilingual—I speak English, Hindi, and Bengali. When I’m messaging my friends and family, we’re basically code-mixing—jumping between languages in the same sentence using the Latin alphabet. Now, my friends and I have noticed that Gboard handles code-mixing much more seamlessly than Samsung Keyboard.

If you just have the English dictionary enabled, neither keyboard can guess that you’re trying to transliterate a different language into English. It’ll always try to autocorrect everything, which breaks the flow. The only way to fix this is by downloading a transliteration dictionary like Hinglish (Hindi + English) or Bangla (Latin). Both Samsung Keyboard and Gboard support these dictionaries, but the problem with Samsung Keyboard is that it can only use one dictionary at a time.

Let’s say I’m writing something in Latinized Bangla and suddenly drop a Hindi phrase. Samsung Keyboard will attempt to autocorrect those Hindi words. Gboard is more context-aware. Since my Hinglish keyboard is already installed, I don’t have to manually switch to it. Gboard can detect that I’m using a Hindi word even with the English or Bangla keyboard enabled, and it won’t try to autocorrect what I’m writing. This also works flawlessly with glide typing, which is a huge quality-of-life improvement over Samsung Keyboard.

This isn’t just an India-specific thing either. Code-mixing is how billions of people type every day—Spanglish in the US, Taglish in the Philippines, Franglais across parts of Europe and Africa.

Gboard looks good without me spending an hour on it

I don’t have time for manual customization

Samsung Keyboard is hands down the more customizable option, especially if you combine it with the Keys Cafe module inside Good Lock. You get granular control over almost every aspect of the keyboard—key colors, keycaps, gesture animations, and a whole lot more. While for some users, this is heaven, I just find it too overcomplicated and a massive time sink.

I don’t have the patience to sit and adjust every visual detail of my keyboard. Sure, it gets stale after a while, and you’d want to freshen it up, but I don’t want to spend the better part of an hour tweaking a virtual keyboard. This is where Gboard wins (at least for me) by doing less.

Android 16 brings Material 3 Expressive, which automatically themes your system apps using your wallpaper’s color scheme. With Gboard, all you have to do is change the wallpaper, and the keyboard updates to match—no Good Lock, no manual color picking. It’s a cleaner, more seamless way to keep your phone looking good without putting in the extra legwork.


The keyboard you don’t think about is the one that’s working

I didn’t switch to Gboard because Samsung Keyboard was broken. I switched because Gboard made typing feel effortless. If you’re a Samsung user who’s never tried it, it’s a free download and a five-second switch. You might not go back either.

Pixel 7 with the 8vim keyboard.


I Tried the Weirdest Android Keyboards So You Don’t Have To

Can strange layouts and gestures beat the good old-fashioned QWERTY?



Source link