Cleaning Up, Mucking Out and Paranoid Programming

Discussion in 'C Programming' started by aarklon@gmail.com, Apr 10, 2008.

  1. Guest

    Hi,

    This talk describes tools and techniques for dealing with large legacy
    code bases. These tools let you go into this code base to figure out
    what is going on with your program.

    Also discussed are techniques for doing paranoid programming designed
    to keep things from getting worse.

    see:-
    http://www.oualline.com/ship/muck/index.html
    , Apr 10, 2008
    #1
    1. Advertising

  2. Richard Bos Guest

    wrote:

    > http://www.oualline.com/ship/muck/index.html


    I paged through to sheet 30 and didn't come across a single point that
    wasn't either obvious or wrong. Also, Mr. Oualline seems, for some
    reason, to think that 120 years is a long time for a bridge to keep
    functioning. He should come to Amsterdam some time.

    Richard
    Richard Bos, Apr 10, 2008
    #2
    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. wired
    Replies:
    35
    Views:
    1,695
    llewelly
    Jul 7, 2003
  2. Doug Rosser
    Replies:
    7
    Views:
    280
    Christopher T King
    Aug 4, 2004
  3. Magnus Henriksson

    Cleaning out my disk

    Magnus Henriksson, Oct 20, 2006, in forum: XML
    Replies:
    3
    Views:
    485
    roy axenov
    Oct 20, 2006
  4. DR
    Replies:
    0
    Views:
    642
  5. Paul Smith
    Replies:
    11
    Views:
    163
    7stud --
    Sep 19, 2009
Loading...

Share This Page