I should also add, keep in mind that sometimes the fundamental problem with the thing you are trying to fix is that there was a design flaw built into the way the original guy attacked the problem and that is why he never got it to quite work.

Instead of just concentrating on a path to fix *his* code, step back for a minute and ask yourself to define what the problem was he was trying to solve and you may see you have to unravel a little of his approach to fix the fundamental flaw in the design.


>Hi everybody,
>
>About 4 business days ago I got a complex footprint assigned to me. There are two forms and one class involved with complex convoluted logic written several years ago by a person who has long since left the company. The class uses gridhittest method.
>
>I've been looking at the code and making numerious changes trying to fix few bugs. Unfortunately, each attempt to fix the problems resolve in something new and ugly surfacing. I am basically ready to give up and ask my manager to assign another developer to this problem. I will release what I currently have, I think.
>
>The problem here is:
>
>1. We need to fix the problem in 2 versions of software. The code base is different, so we would need to apply similar fixes in two versions
>
>2. I've been working with the latest version and, as I said, made a numerous changes. At this point I am not even sure that all of my changes are correct or if they solve the problem or introduce the new one.
>
>I am wondering how to handle such situation and admit that I am beaten here?
>
>Also, I've been working on C# code for a while, but because I got that assignment, I had to put that project aside for the time being.
>
>Any ideas?
>
>My manager is a very nice person and I guess I can call her and tell that I need a break from this assignment. Just need to get up the courage to call. I am also not certain how will it work.
>
>Thanks in advance.