DevX Home    Today's Headlines   Articles Archive   Tip Bank   Forums   

Results 1 to 2 of 2

Thread: Good points

  1. #1
    PDezenzio Guest

    Good points


    Brad brought up some good reasons on why an IDE shouldn't be used, but I also
    have as many reasons why they should be used. Here's a couple of the big
    ones:

    1. Increased productivity.

    I have more books on Java than even my decades of experience on the Mainframe
    had accumulated. Everytime a new release comes out, I have to re-purchase
    new books. With JBuilder 6.0, all I have to do is point my IDE to the new
    JDK and I have everything I need to pull up any classes and all their method
    signatures. You can't do that with a text editor (if emacs can, let me know!!).
    Also, JBuilder provides the mechanism to bring in 3rd party tools that can
    be used to format code as per one corporate standard or to insert JavaDoc
    automatically. Again, can't be done with a text editor although there are
    other tools that can aid a text editor.

    2. Increased productivity, Part 2.

    JBuilder's ability to step through code is the primary reason we use an
    IDE. Without it, it takes anywhere from 10 minutes to 8 hours to find a
    bug. With it, within minutes. I saved 4 man days' with JBuilder via the
    debugging feature alone on my current project!! It takes a bit of setting
    up, but once you have it, you won't leave it. I agree that it can make a
    developer lazy, but clients first and foremost want the project completed
    on-time. Telling a client that you prefer a text editor because of the purity
    of development, but it can take longer to complete a project, won't sit well
    with them. I don't have all day to debug 2,000 lines of code.
    Our average time to implement 15,000 line projects is under 5 months with
    2 developers.

    The reasons for using or not using an IDE differ depending on what you do
    as a programmer. If you are a consultant, and jump from one assignment to
    the next, then using a text editor might be the better option. My reasons
    pertained to those of us who are regular full-time employees and to those
    that have longer-term assignments. It was our contractors that opened us
    to using JBuilder even though they are all Unix-loving analysts. It all
    comes down to user preference. I did like your reasons and they are valid,
    but anyone can make a case for or against using IDEs. I do use Ultra Edit
    quite often, especially when I designed a JSP/Servlet system last year.
    Certain tasks demand different tools and a good developer learns to use all
    of them.

    Patrick Dezenzio
    Systems Analyst
    Blue Cross Blue Shield of Alabama

  2. #2
    MarkN Guest

    Re: Good points


    Well said. In addition - one reason I am a consultant/contractor (and what
    I think makes me good and marketable) is because I am a quick learner. A
    new IDE is nothing for quicker learners. On the other hand APIs are more
    difficult to learn and take much more time. A good IDE, as Patrick describes,
    will really cut this time down.

    IDE's/Case Tools I know and use(d) - VB3-to-6, Powerbuilder, VS.Net, Visualage,
    WSAD, NetBeans, Pacbase, CodeWarrior, FoxPro, a couple of C/C++ tools, Report
    builders (Crystal Reports, ...), etc. Some I know better than others. Some
    I am trying to forget. Guess how many years I've been progamming?


    "PDezenzio" <pdezenzio@bcbsal.org> wrote:
    >
    >Brad brought up some good reasons on why an IDE shouldn't be used, but I

    also
    >have as many reasons why they should be used. Here's a couple of the big
    >ones:
    >
    >1. Increased productivity.
    >
    > I have more books on Java than even my decades of experience on the Mainframe
    >had accumulated. Everytime a new release comes out, I have to re-purchase
    >new books. With JBuilder 6.0, all I have to do is point my IDE to the new
    >JDK and I have everything I need to pull up any classes and all their method
    >signatures. You can't do that with a text editor (if emacs can, let me

    know!!).
    > Also, JBuilder provides the mechanism to bring in 3rd party tools that

    can
    >be used to format code as per one corporate standard or to insert JavaDoc
    >automatically. Again, can't be done with a text editor although there are
    >other tools that can aid a text editor.
    >
    >2. Increased productivity, Part 2.
    >
    > JBuilder's ability to step through code is the primary reason we use an
    >IDE. Without it, it takes anywhere from 10 minutes to 8 hours to find a
    >bug. With it, within minutes. I saved 4 man days' with JBuilder via the
    >debugging feature alone on my current project!! It takes a bit of setting
    >up, but once you have it, you won't leave it. I agree that it can make

    a
    >developer lazy, but clients first and foremost want the project completed
    >on-time. Telling a client that you prefer a text editor because of the

    purity
    >of development, but it can take longer to complete a project, won't sit

    well
    >with them. I don't have all day to debug 2,000 lines of code.
    >Our average time to implement 15,000 line projects is under 5 months with
    >2 developers.
    >
    >The reasons for using or not using an IDE differ depending on what you do
    >as a programmer. If you are a consultant, and jump from one assignment

    to
    >the next, then using a text editor might be the better option. My reasons
    >pertained to those of us who are regular full-time employees and to those
    >that have longer-term assignments. It was our contractors that opened us
    >to using JBuilder even though they are all Unix-loving analysts. It all
    >comes down to user preference. I did like your reasons and they are valid,
    >but anyone can make a case for or against using IDEs. I do use Ultra Edit
    >quite often, especially when I designed a JSP/Servlet system last year.


    >Certain tasks demand different tools and a good developer learns to use

    all
    >of them.
    >
    >Patrick Dezenzio
    >Systems Analyst
    >Blue Cross Blue Shield of Alabama



Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
HTML5 Development Center
 
 
FAQ
Latest Articles
Java
.NET
XML
Database
Enterprise
Questions? Contact us.
C++
Web Development
Wireless
Latest Tips
Open Source


   Development Centers

   -- Android Development Center
   -- Cloud Development Project Center
   -- HTML5 Development Center
   -- Windows Mobile Development Center