Search:

Type: Posts; User: KevinWorkman

Search: Search took 0.08 seconds.

  1. Replies
    17
    Views
    2,580

    Re: When *Not* to Use an IDE

    Either way works- you can pass the command line arguments into the program, or you can read them in after the program starts running using something like the Scanner class.
  2. Replies
    17
    Views
    2,580

    Re: When *Not* to Use an IDE

    The only thing a debugger lets you do is examine the code line by line as it's being run. It doesn't spot bugs or get rid of them automatically, but it does make it easier for you to figure out the...
  3. Replies
    17
    Views
    2,580

    Re: When *Not* to Use an IDE

    To be fair, the people I was talking about were people I went to school with, not people I work with. In my senior year of college, it really shocked me how little my peers knew about programming-...
  4. Replies
    17
    Views
    2,580

    Re: When *Not* to Use an IDE

    I should have also made this more clear in the original post as well, but this was just my approach, and it seems to have worked for me. I have seen other people really handicap themselves by taking...
  5. Replies
    17
    Views
    2,580

    Re: When *Not* to Use an IDE

    I should have made this more clear in the original post, but things like jEdit will do auto-formatting and syntax highlighting for you, without any of the extra bells and whistles. I use jEdit and...
  6. Replies
    17
    Views
    2,580

    When *Not* to Use an IDE

    I’ve been asked to make a post on the dangers of relying on an IDE, so here goes…

    Tl;dr version: Relying too heavily on an IDE makes you a bad programmer. To demonstrate my point, think about...
Results 1 to 6 of 6