Work problem fix in the works
Oct. 3rd, 2003 09:59 am![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
fuzzygrufYesterday was entirely too stressful. With databases and screens hosed, I had more adrenalin going than in ages. About 3pm, Ben finally came over to help me. (I had emailed for his help around 6:30am.) Turns out that the impact is fairly small, only about 20 accounts. He had talked to the user, and it was easy for them to do manual calculations. Whew. That was a big relief. He verified the fix changes with me, which were simple. Now we just need to go through a zillion approvals, and the change will be installed next week.
I was totally perplexed with why the problem occurred. I reviewed it with Ben, and he agreed that my installed changes were the correct logic. It turns out that after I had checked out the program from production, someone had altered a few lines of code before I made the changes. I made my changes based on the altered code. No way to tell who altered the code if it's not notated. At my former job, only the person who checks out the program has access to it. No such security measures in place here.
Anyhow, after talking to Ben, the stress went away. Whew.
I was totally perplexed with why the problem occurred. I reviewed it with Ben, and he agreed that my installed changes were the correct logic. It turns out that after I had checked out the program from production, someone had altered a few lines of code before I made the changes. I made my changes based on the altered code. No way to tell who altered the code if it's not notated. At my former job, only the person who checks out the program has access to it. No such security measures in place here.
Anyhow, after talking to Ben, the stress went away. Whew.
