# TDD: Test-Driven? Nope. Tab-Driven Development!

You’ve heard of **Test-Driven Development**, but have you tried **Tab-Driven Development**?

It’s simple: just `tab tab tab`, and your cursor magically jumps to the next thing to change. Who needs precision when you can just `tab` your way to success?

I first saw this feature in the [Cursor](https://www.cursor.com/features) editor, and honestly, it was a game-changer. This saves time and understand the content where your cursor at. It’s extremely useful when you’re refactoring code or repeating some boring/repetitive task.

[![Image from Gyazo](https://i.gyazo.com/06f68ebaed93ac54560f971d07da9de4.gif align="left")](https://gyazo.com/06f68ebaed93ac54560f971d07da9de4)

That was also when I *almost* made the switch from Neovim to Cursor (a VS Code fork). *Almost.* Don’t worry, I’m still a Neovim user… 😆

Cursor pioneered this feature, but now, every IDE is jumping on board. Recently, VS Code rolled out a similar update:

%[https://youtu.be/C95drFKy4ss?si=wm4Hj2JKgEjnkgTS] 

Other editors like [Windsurf](https://codeium.com/windsurf) are catching up too:

[![Image from Gyazo](https://i.gyazo.com/923ac854e5bc0e1d0f93cd75aa48a03b.png align="left")](https://gyazo.com/923ac854e5bc0e1d0f93cd75aa48a03b)

Even [Zed](https://zed.dev/), my *second* favorite IDE (don’t ask who’s first 😉), has introduced the **Zeta model** with [edit prediction](https://zed.dev/blog/edit-prediction).

If you’re curious about my Cursor setup, you can find it here: 👉 [https://github.com/jellydn/vscode-like-pro](https://github.com/jellydn/vscode-like-pro)

Tab-driven editing is becoming a must-have feature for modern IDEs. Is it life-changing or just a fancy autocomplete? Let me know your favorite!

Cheer and happy coding!