I recently started moving from Eclipse CDT to Zed for my C++ development.
On the surface, it is just an IDE change.
For me, it is something more.
Eclipse CDT has been a trusted companion for years. Projects, indexing, debugging, builds, refactoring—everything became familiar. And that familiarity is comfortable.
But there is a danger in becoming too comfortable with the tools.
Moving to Zed has made me revisit the fundamentals:
C++ → CMake → Ninja → compiler → linker → debugger → Git → clangd
Suddenly, things that had become invisible are interesting again.
How does clangd understand my project?
What exactly does CMake generate?
How does the debugger interact with my program?
How much of an IDE do I actually need?
These are not merely editor questions. They are engineering questions.
And perhaps that is what I enjoy most.
As engineers gain experience, there is a risk of becoming operators of familiar systems rather than explorers of new ones.
I don't want that.
The move from Eclipse to Zed is therefore not really about:
Eclipse → Zed
It is about:
Routine → Exploration
Familiarity → Curiosity
"This is how I always do it" → "What happens if I try this?"
The tools will keep changing—C++, compilers, build systems, editors, AI, GPUs, simulation frameworks.
The important thing is to keep experimenting.
Because after years of programming, discovering a new tool is nice.
But discovering that the explorative engineer inside me is still alive—and thriving is much better.