[Nab443]

This is the point, you need an IDE with advanced features while a text editor should be all you need to understand what the code is doing..

[sverhagen]

Why, as a professional, would you not use professional tooling. Not just for DI, but there are many benefits to using an IDE. If you want to hone your skills in your own time by using a text editor, why not. But as a professional, denying the use of an IDE is a disservice to your team. (But hey, everyone's entitled their opinion!)

Edit: upon rereading I realize your point was about reading code, not writing it, so I guess that could be a different use case...

[jen20]

Being able to understand a system under fire with minimal tooling available is a property one must design for. If you get woken up at 3am with a production outage, the last thing you want to do is start digging through some smart-ass framework's idea of what is even running to figure out where the bug is.

There's nothing wrong with using an IDE most of the time, but building dependence on one such that you can't do anything without it is absolute folly.