Perform a full design and/or code review on the broken code  Throw away the section of code and redesign/recode it from scratch  Throw away the whole program and redesign/recode it from scratch  Compile code with full debugging information  Compile code at pickiest warning level and fix all the picky compiler warnings  Strap on a unit test harness and test the new code in isolation  Create an automated test suite and run it all night  Step through a big loop in the debugger manually until you get to the error condition  Instrument the code with print, display, or other logging statements  Replicate the end-user’s full machine configuration  Integrate new code in small pieces, fully testing each piece as its integrated from book...

Few companies that installed computers to reduce the employment of clerks have realized their expectations.... They now need more, and more expensive clerks even though they call them "operators" or "programmers."  ~Peter F. Drucker Programmer - an organism that turns coffee into software.  ~Author Unknown Programming is like sex.  One mistake and you have to support it for the rest of your life.  ~Michael Sinz All programmers are playwrights and all computers are lousy actors.  ~Author Unknown Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live.  ~Martin Golding Everyone knows that debugging is twice as hard as writing a...

I am able to finish Chapter 6 - While you are coding and  Chapter 7 - Before the Project . These chapters triggered my understandings about the topics and made me reconsider everything I know about software development , requirement analysis , tools etc. . I would like to give a sneak preview what I have been reading so far. On Chapter 6 ,Programming by coincidence is my current favorite. It explains why some piece of code might works or assume the code is working. I was shocked and confused when I first read the title, but whenever I went into...

I have started to read The Pragmatic Programmer about a week ago , and still trying to finish. I am current at Chapter  5 , "Bend or Break". Since now , it has been quite a nice journey to read the chapters. Although the book has been written at 1999 , it is pretty much actual. What this book gives us is the phylosophy behind the software development , ways to improve ourselves in daily basis , easify our job , solid tecniques to more flexiable , adaptable , configurable software development. Also includes a lot of suggestions to improve...

I have started to read The Pragmatic Programmer about a week ago , and still trying to finish. I am current at Chapter  5 , "Bend or Break". Since now , it has been quite a nice journey to read the chapters. Although the book has been written at 1999 , it is pretty much actual. What this book gives us is the phylosophy behind the software development , ways to improve ourselves in daily basis , easify our job , solid tecniques to more flexiable , adaptable , configurable software development. Also includes a lot of suggestions to improve...