Interview with the Java Bug Guy

Discussion in 'Java' started by Veloso, Apr 18, 2007.

  1. Veloso

    Veloso Guest

    Sun's Java site, java.sun.com, has an interesting interview (http://
    java.sun.com/developer/technicalArticles/Interviews/community/
    harry_qa.html) with Brian Harry, a.k.a. the "bug guy," who talks at
    length about how he fixes bugs. Harry, an independent consultant from
    Iowa, fixed Java SE 6 bugs numbering into the hundreds. His method: he
    scanned Sun's openly available bug database for intriguing bugs,
    primarily in the Swing user interface code, printed them out, and put
    the bug reports on a stack beside his computer. Then, he fixed them
    one by one, submitting them through the standard JDK Community
    contribution process.

    The interview gives the details:

    * He points out that fixing bugs is a great way to understand how the
    code works. To James Gosling's bug rule, "If you don't see the bug
    where you're looking, perhaps you're looking in the wrong place."
    Harry adds: "The place where you find bugs may not be the right place
    to put a fix in"

    * His basic advice: "First, always acquire the test that's attached to
    the bug report... Next, ask yourself if it's really a bug... Also,
    consider writing different solutions... As to writing unit tests, look
    at what the patched code interacts with."

    * Swing tip 1: "Try to be comprehensive in testing the patch with
    different LAFs (Look and Feels)."

    * Swing tip 2: "Make sure that the test case is running on the EDT
    (event dispatch thread). If it isn't, you may not have a bug, but
    instead just have bad programming."

    * "If you're doing a Java code fix, don't just look at the current
    version of the platform. I've routinely tested out bug tests on 4, 5,
    and 6 to investigate when a problem started and stopped. See if you
    can find why something started."

    I'm just starting to look at the Swing code, which feels a bit
    overwhelming. Harry advises that Swing hackers map out the
    relationship between the Swing class and its UI and says that to be an
    effective Swing hacker, you need to know what's coming from what.

    Anybody with more experience have comments on all of this?
     
    Veloso, Apr 18, 2007
    #1
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Replies:
    4
    Views:
    541
    Chris Uppal
    May 5, 2005
  2. Replies:
    2
    Views:
    500
  3. Macon Joe Job Guy Joe Macon Job Guy

    Att: Macon Joe Job Guy Joe Macon Job Guy Macon

    Macon Joe Job Guy Joe Macon Job Guy, Oct 14, 2007, in forum: Java
    Replies:
    0
    Views:
    380
    Macon Joe Job Guy Joe Macon Job Guy
    Oct 14, 2007
  4. reema
    Replies:
    0
    Views:
    293
    reema
    Aug 26, 2008
  5. Replies:
    1
    Views:
    222
    Rectal Mania
    Aug 6, 2007
Loading...

Share This Page