I stopped using IDEs as a

@daniallqureshi

9.8K followers · usually 4.2K views a post

Views

146.6K

Likes

6.4K

Comments

600

Shares

187

SoundTikTok sound · original sound - daniallqureshi

View velocity

+86.6K views over 19.7d · ~4.4K/day · 18 observations

Why it worked

The video challenges a common practice in software engineering, presenting a contrarian viewpoint that sparks curiosity and debate. By establishing credibility and offering a forward-looking perspective on AI integration, it resonates with developers seeking efficiency and modern workflows.

Summary

A software engineer explains why they stopped using traditional IDEs, arguing that their primary purpose is to write code, which can now be handled by AI. They highlight that features like diffing and git branching are secondary and that modern terminal tools and AI code reviewers are sufficient for their needs.

Structure

1Stating the controversial claim of stopping IDE use
2Addressing the 'vibe coder' label
3Establishing credibility as an experienced engineer
4Defining the core purpose of an IDE (writing code)
5Explaining the sufficiency of AI and terminal tools for coding tasks
6Advocating for embracing modern tooling and adapting to change

On-screen text

I stopped using IDEs as a Software Engineer

Original caption

It’s forward looking to start letting go of tooling that you no longer need. This forces you to become more versed in modern tooling and development practices. Times are changing and you need to change with them. #fyp #softwareengineer #ai #coding

More from @daniallqureshi

More breakout videos from this creator.

Transcript

I said I stopped using an IDE as a software engineer and people are calling me a vibe coder. I'm not a vibe coder. I've been a software engineer for over 6 years. I've been a FAANG engineer for over 5 years. So I know software engineering. Here's my point. What's the point of an IDE? The primary purpose is to write code. Everything else is an extra feature. The diffs, the git branching, all of that stuff, that's extra. The primary purpose is to write code, which we no longer do. And so I do not need to open an IDE to write code. I can just prompt the AI to do it. I have tools in the terminal that allow me to review the diff of the AI generated code. I also have the code reviewer/pull request tool in which I can review the code and I get to see the AI review comments there to make sure that the code that I actually merge into prod is robust and maintainable. I do not need a full blown IDE anymore to do the coding work of a software engineer. It's forward looking to start letting go of tooling that you no longer need. This forces you to become more versed in modern tooling and development practices. Times are changing and you need to change with them.