A debugging story.

N

Neil Cerutti

I just spent two hours debugging a crucial, though fairly simple,
program.

As part of the processing of an admissions report, I use difflib
to compare two csv files. I compare the current
file with one from the immediate past. The file changes over time
as new students are accepted, and current students change major
and so forth. I next comb through the generated diff to find the
actually changed fields, keeping a log of critical changes.

I found I had not accounted for field names changing between runs
of the admissions report, as recently happened when something had
to be added to the report.

I finally got it working and tested, and then was horrified when
a slip of my finger caused me to have to revert to a previous
version of the file from rcs. Two hours of work, down the
bit-bucket!

My horror abated when I found I was able to make the necessary
changes again in roughly 30 seconds.

This message brought to you by the Debugging is Mostly
Comprehending Old Code and Testing Council.
 

Ask a Question

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

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

No members online now.

Forum statistics

Threads
473,982
Messages
2,570,186
Members
46,744
Latest member
CortneyMcK

Latest Threads

Top