Debugging

Categories: Technology, Work
Comments: 2 Comments
Published on: August 18, 2005

I was angry with myself today. I spent 2 days debugging my code because I believed that there was an error in the code, because it was not working the way I wanted it to work. I kept going though all the objects and the code, and could not figure out why what was wrong with the code. Today around 3 I figured out what the problem was. The code was working perfectly, it was the configuration file that I was reading it prevented what I wanted to happen from happening, and the code was perfect. I was able to show that the code was working and was able to show that if the data of the config files were different that the thing I wanted to happen would have happened.

2 Comments
  1. Jimmy Cerra says:

    I know what that’s like – doing the same myself. I guess config files need unit tested the same as regular code.

    Got a quick question… what makes a framework lightweight? I never really understood what that meant.

  2. Max Rossin says:

    Ah debugging, there should be a blog about programming problems. I spent an hour once figuring out why my software didn’t work. Turns out I had “=” instead of “==”… oh how sad… I had to get off the chair and leave the cube. Most of the time though, it’s like a miracle: I write 20 pages of code and it works flawlessly from the first time. Almost makes me cry. Almost.

Welcome , today is Monday, April 24, 2017