4 ms·
It’s a lot of small things, so here are some examples: * Click to find usage is exceptionally good. * when refactoring, it will also find associated files/cla
by SkyPuncher 2y ago
It’s a lot of small things, so here are some examples:
* Click to find usage is exceptionally good.
* when refactoring, it will also find associated files/classes/models and ask you want to change them as well. It’s also smart enough to avoid refactoring things like database migrations
* Click-run just about anything is amazing. I work in multiple languages in multiple code bases. I get tired of figuring out how to install packages, run things, and even get into debug mode. Most major tooling is supported out of the box.
* Debugging. Lots of data types have smart introspection when debugging. It knows that Pandas tables should be opened in a spreadsheet, JSON should be automatically formatted, and you really just want that one property in a class already formatted as a string.
* Built in profilers and code coverage. This is something that’s always annoying to switch tooling with.
* Great Git integration, though that’s probably par for the course.
* Database integration in some toolsets (like Rails). If you need to look at records in the database, it will jump you directly to the table you need with Excel-style filters
* Local history on just about everything. This has saved my butt so many times. You can delete an entire folder and know you can restore it, even if you delete it from Git.
* Automatic dependency change detection. For example, after a pull, it will identify if new or updated updated dependencies were pulled. 1-click to install.
* Type hinting in in-type languages