Debugging leads to buggy code and longer hours?

This is a discussion on Debugging leads to buggy code and longer hours? within the A Brief History of Cprogramming.com forums, part of the Community Boards category; thats right! read it again!! im not crazy! no,no,put down the stakes and hear me out! i really am beginning ...

  1. #1
    Has a Masters in B.S.
    Join Date
    Aug 2001
    Posts
    2,267

    Debugging leads to buggy code and longer hours?

    thats right! read it again!! im not crazy!

    no,no,put down the stakes and hear me out!

    i really am beginning to think that being able to debug your code for errors every two lines leads you to be sloppy since you "know" the debugger will save your ass every time and you can go through and fix as you go.

    heres my backup,

    EXPERIENCE:

    i've been coding for what? 3-5+ years? im not sure anymore its been so long...

    anyway i've notice when i code without ever debugging only using a compile to check for basic errors but NEVER running or debugging the code i get much better more efficient bugfree code

    i just recently wrote 300+ lines of virtually BUG FREE(i've done this before) code and i have troughly tested it and found NO BUGS!NONE!!!, anyways i do this a lot when i have no choice but to, especially when im to lazy to wright a driver to test it as soon as im done, i get better thought out, more efficient, shorter code than when i do with the run and debug method!

    anyone else have this problem? am i just insane?
    Last edited by no-one; 01-28-2002 at 12:26 AM.
    ADVISORY: This users posts are rated CP-MA, for Mature Audiences only.

  2. #2
    A Banana Yoshi's Avatar
    Join Date
    Oct 2001
    Posts
    857
    Most people get more bugs when debugging... You are indeed special.
    Yoshi

  3. #3
    Registered User
    Join Date
    Sep 2001
    Posts
    752
    ...
    Isn't this kinda like saying a lack of fire-trucks in the neighborhood leads to less fires?

    Buggy code leads to debugging. The debugging itself is pretty nice, since it makes the failings of the programmer dreadfully obvious, hence leaving room for improbement.
    Callou collei we'll code the way
    Of prime numbers and pings!

  4. #4
    Mayor of Awesometown Govtcheez's Avatar
    Join Date
    Aug 2001
    Location
    MI
    Posts
    8,825
    Debugging makes buggy code? Somehow I doubt it...

    Don't like the debugger? Don't use it.... (I, for one, would kill to have one with this compiler)

  5. #5
    Code Goddess Prelude's Avatar
    Join Date
    Sep 2001
    Posts
    9,796
    If you want bugless code then THOROUGHLY design your program and check for all problems, come up with alternatives if something won't work and do paper runs before even typing one character.

    Past that it should only be removing syntactic errors and finger slips. I love my debugger, but I love my lint even more. There's no high like getting 500 errors from your standard header file with the hello world program.

    Not debugging simply because you think it will cause less bugs is dangerous. The last thing you want is for a customer to find your obscure bugs and complain to your boss about it.

    -Prelude
    My best code is written with the delete key.

  6. #6
    Has a Masters in B.S.
    Join Date
    Aug 2001
    Posts
    2,267
    you misunderstand me im saying if i write the code without debugging it untill im finished it comes out better than if i debug it a lot during developement,

    I ALWAYS DEBUG AFTER IM DONE!!
    ADVISORY: This users posts are rated CP-MA, for Mature Audiences only.

  7. #7
    Mayor of Awesometown Govtcheez's Avatar
    Join Date
    Aug 2001
    Location
    MI
    Posts
    8,825
    Oh, well ALRIGHT THEN!

    That makes sense - you're not stopping and starting every couple minutes, so your code flows better with your train of thought...

Popular pages Recent additions subscribe to a feed

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21