True, though the concept of an IDE is pretty ancient and stems from MS-DOS where because it lacked true multi-tasking you could only run *one* program, it had to be all integrated into one monolithic thing. I actually learned on the Borland C++ 3.1 IDE first but then switched to the more modular tools (i.e vi, cc, grep, etc) much later because I realized it was a more efficient workflow and I was able to easily access "modern" workstations (that said, Watcom vi, wcl and wgrep were great tools for DOS. Coupled with DESQview, offers better tooling than I see most of my collegues using over 20 years later!).With modern IDE's however there is no need for all that. [...]
Many have no idea of what is going on underneath that IDE
A lot of IDE guys think they can stay confined to an IDE. But only because they leave the hard tasks to those with a little bit more of indepth knowledge of the underlying tools. Things like setting up build systems, remote debugging, complex VCS processes simply are out of reach.