3 ms·
Out of interest, do those who don't use IDE's use a step through debugger? This is my main reason for using one, plus I quite like being able to set things up a
by collyw 12y ago
Out of interest, do those who don't use IDE's use a step through debugger? This is my main reason for using one, plus I quite like being able to set things up and just press a button, rather than type a command every time I want to re-run my application.
- MichaelCrawford 12y agoThe main reason that I am able to do without IDEs most of the time, is that it is uncommon for me to use debuggers anymore. For the most part I use assertions. Quite commonly all I require is to assert the validity of input parameters to subroutines. Less commonly I do that for return values. Uncommonly I use insertions somewhere in the middle. Very rarely - but sometimes - I use class invariants. That is, a circle class has an invariant that its radius is fixed all the way around; that's not the case for ellipses. However when I do use class invariants, they are very helpful. I also use memory debuggers like guard malloc and valgrind. It's not that I don't use step-through debuggers at all, but with all the above it is uncommon that I feel the need to.
- notduncansmith 12y agoComing from a Node.js background, I use a text editor, and debug with Chrome using node-inspector. In other languages (Ruby, Elixir, Clojure), I just debug with print (and make heavy use of the REPL). As for buttons vs commands, I suspect that's largely a preference thing (believe me, I thought hard about refuting the buttons because I personally dislike them, but eh, different strokes). I have shell aliases for most of my common commands, and if something needs to run continuously or on save, it's pretty easy to write a script or Gulpfile that'll do that for me. For anything else, it's uncommon enough that it'd be a menu item (hopefully!) anyways, not a button, so I'm unlikely to see any effort savings from using an IDE vs the terminal.
- collyw 12y agoYes, I have a few shell aliases for commands with a load of parameters I use. I suppose setting up Eclipse versus writing a few aliases is probably about equivalent. Debugging with print can only get you so far. I use Django which is a big framework, so I couldn't understand the code without a proper step through debugger. I would say its been essential to get to the understanding I have now of forms and class based views.
- notduncansmith 12y agoI agree. Beyond the preference aspect there's definitely a notion of using the right tool for the job - and in an unfamiliar codebase (e.g. one that relies on a heavy framework like Django filled with thousands of lines of code I've never seen), as I mentioned before an IDE can be of significant benefit. That said, once one has grokked the framework to a fair degree, I would imagine that continuing benefit (in that respect) would be quite limited.