I am engaged in a project at work where I am unraveling someone else's code and knitting it back together in a fashion where it will be much easier to trace through the bits of yarn when I'm done. Unfortunately, it's not trivial in any sense.

But I am making progress.

Slowly. Very slowly.

I actually don't so much mind refactoring code, as long as I am doing something that will improve the code base. For instance, today I worked with one of my colleagues to convert a reference to a particular class to a reference to a shared interface implementation. This was good, because now anyone else who has the same problem will be able to ( Read more... )

Another round of fixes destined for an emergency patch that I spent most of the day hacking out with one of my co-workers. The code in the neighborhood is much cleaner now -- I wrote this fairly early in my Java adventure and was able to make a bunch of fairly trivial, but major improvements while cleaning up the bad behavior that was going on. ( Read more... )

And today was back to work (and school) after a two-week break. There were varying degrees of success.

On the other hand, I finally threw up my hands and stopped trying to add a remove method to my Java iterator built on top of my unifying interface layer. Instead, I've coded things using a different approach to what I'm doing.

I've managed to ( Read more... )

I may be getting tired of the bugs coming in, but apparently they are not tired of me.

Ah, well. I was able to patch things around so that I could read the seriously damaged file I was sent this morning. Now if only the rest of the code would behave itself... :)

I have been fixing a silly number of bugs in the last couple of days.

One of the bugs that I am fixing right now is one that I thought was going to be a horrible amount of work. It turns out that I can fix it rather simply, which I found out after digging through the code.

I just can't *test* the fix, for reasons having to do with Microsoft Excel's ( Read more... )

I am still crawling through our user-interface code. I have cleaned up a great many things, but there are some interactions that are perplexing me. I think I have some ideas about how to proceed, but I'd like to talk with one of the fellows who wrote it.

I'd like to give it back to him, actually. We'll see how that goes. :)

I have fixed a great many bugs this week.

Right now, I'm looking at the debris in our Visual Studio 2019 port. The COM handling machinery there seems a bit idiosyncratic, but it's possible to work around those eccentricities once you find them. I'm doing bulk corrections and it seems to be stable.

But I've found some code in our UI layer that I ( Read more... )

I am trying to write a new bit of code to make a particular interface work, but the code that I write isn't working (or apparently called) even though it seems to have all of the necessary elements for this particular incantation.

I am annoyed.

I'll try this again tomorrow.

I cleaned up a bunch of crufty, slow code in our user interface layer over the last week and checked the changes in today. There are still some more places that can be cleaned up, but I took care of a lot of the low-hanging fruit.