What do you really get from IDE-driven development?
It seems like the author understands, or perhaps his criteria is based on, only a thin layer of what an IDE can provide. Here&#x27;s the highlights:<p>- Data flow to&#x2F;from here (where did the value of this variable come from&#x2F;go to)<p>- Call hierarchy (up and down)<p>- Class hierarchy (up and down)<p>- Class structure (including all inherited fields, methods)<p>- Checking your code against an actual database schema, perhaps one automatically launched in a Docker container<p>- Automatic refactoring of various kinds (rename, extract variable, extract method, inline method, extract interface, add&#x2F;remove parameters, etc.)<p>- Build tool dependency tree inspection with filtering etc.<p>- Inspect code for a huge variety of potential code quality issues, with highlighting and auto-resolutions available<p>- Locate duplicate code, and automatically refactor it out<p>- Detect likely problems with nullity<p>- Easily navigate to lines of code in an exception call stack<p>- Analyze dependencies across classes &amp; packages, detect cyclical dependencies<p>- Debugging, including watch windows and conditional breakpoints of various kinds<p>- Helpful tools for a variety of programming frameworks such as Spring<p>- Integration with git so you can view history, diffs, etc.<p>- WYSIWYG style rendering for stuff like Markdown<p>- Easily navigate to any class, including classes that come from your dependencies (for example I&#x27;ve worked with plenty of people who had no idea how to figure out how Rails worked if it wasn&#x27;t in the documentation, because they didn&#x27;t use an IDE which allowed them to easily browse the code)<p>Personally, all of that is just a huge amount of value.